Triple
T37276197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Almeida family |
E924653
|
entity |
| Predicate | notableBranchActivity |
P205813
|
FINISHED |
| Object | military service |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: military service | Statement: [Almeida family, notableBranchActivity, military service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBranchActivity Context triple: [Almeida family, notableBranchActivity, military service]
-
A.
notableBranch
Indicates that one entity is a particularly significant or prominent subdivision, offshoot, or branch of another entity.
-
B.
notableFork
Indicates that one entity is a significant fork or derivative version of another, typically diverging in a notable or influential way from the original.
-
C.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
D.
affectedBranch
Indicates that one entity is a branch that is impacted or influenced by the state or actions associated with another entity.
-
E.
influencedBranch
Indicates that one branch, idea, or development has been shaped or affected by another preceding or related branch.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:16 p.m.