Triple
T12727927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Review of the Armies in Washington, D.C., 1865 |
E304153
|
entity |
| Predicate | reviewingStandLocation |
P65992
|
FINISHED |
| Object | in front of the White House |
—
|
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: in front of the White House | Statement: [Grand Review of the Armies in Washington, D.C., 1865, reviewingStandLocation, in front of the White House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reviewingStandLocation Context triple: [Grand Review of the Armies in Washington, D.C., 1865, reviewingStandLocation, in front of the White House]
-
A.
examinationLocation
Indicates the place or setting where an examination or test is conducted.
-
B.
operationLocation
chosen
Indicates the place or site where an operation, activity, or process is carried out.
-
C.
heldAtLocation
Indicates that an entity is being kept or stored at a specific location.
-
D.
slotLocation
Indicates the specific position or compartment within a larger container or system where an item is placed or assigned.
-
E.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.