Triple
T32184757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Column |
E822077
|
entity |
| Predicate | marchedThrough |
P168869
|
FINISHED |
| Object | Arizona Territory |
—
|
NE NERFINISHED |
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: Arizona Territory | Statement: [California Column, marchedThrough, Arizona Territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marchedThrough Context triple: [California Column, marchedThrough, Arizona Territory]
-
A.
marchedOver
chosen
Indicates that one entity moved in a marching manner across or past another entity or location.
-
B.
performsMarches
Indicates that an entity carries out or participates in organized marches, such as processions, parades, or protest demonstrations.
-
C.
regimentalMarch
Indicates a coordinated, rhythmic movement of a group in formation, typically following strict timing and alignment as in military drill.
-
D.
musteredIn
Indicates that an individual or unit was formally enrolled, assembled, or brought into active service within an organization, typically a military force.
-
E.
corpsMarch
Indicates that a military corps is performing the action of marching.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bab9100c8190ad1f86fece0fc505 |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:35 a.m.