Triple
T2980195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlington Estate |
E80489
|
entity |
| Predicate | functionDuringCivilWar |
P19322
|
FINISHED |
| Object | Union military headquarters vicinity |
—
|
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: Union military headquarters vicinity | Statement: [Arlington Estate, functionDuringCivilWar, Union military headquarters vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuringCivilWar Context triple: [Arlington Estate, functionDuringCivilWar, Union military headquarters vicinity]
-
A.
functionAfterCivilWar
Indicates that one entity serves or operates in a particular function, role, or capacity following the end of a civil war.
-
B.
functionDuringRevolution
Indicates that an entity performs or serves a particular function specifically during a revolutionary period or event.
-
C.
statusDuringWar
chosen
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
D.
functionDuring1865
Indicates that a function, role, or activity was performed or in effect during the year 1865.
-
E.
civilWarPeriod
Indicates a time span during which a civil war is occurring or in effect.
- F. None of above.
Provenance (3 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999e91788190a2d430dd0600a660 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.