Triple
T32184838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California volunteer cavalry |
E822079
|
entity |
| Predicate | locationOrganized |
P13661
|
FINISHED |
| Object | California |
E1909002
|
NE 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: California | Statement: [California volunteer cavalry, locationOrganized, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOrganized Context triple: [California volunteer cavalry, locationOrganized, California]
-
A.
locatedInOrganizationally
Indicates that one entity is organizationally situated within, or belongs to, another entity in terms of administrative or structural hierarchy.
-
B.
organizationalPlacement
Indicates how an entity is positioned or situated within an organization’s structure or hierarchy.
-
C.
organizationLocatedAt
Indicates that an organization is situated or based at a specific geographic location or address.
-
D.
managingOrganizationLocation
Indicates that an organization has managerial or administrative responsibility over activities or operations occurring at a specified location.
-
E.
locationFormed
chosen
Indicates the place or geographic area where an entity (such as an organization, group, or structure) was originally established or came into existence.
- F. None of above.
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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0224f4b6cc8190a8f79700a9af765f |
completed | May 11, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0be4f74081909f8af554738dcd31 |
completed | June 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_6a0223f01eb081909419518fdd45f2a4 |
completed | May 11, 2026, 6:46 p.m. |
Created at: May 1, 2026, 12:35 a.m.