Triple
T27438720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 400 |
E690863
|
entity |
| Predicate | stateWithMajorExtent |
P32975
|
FINISHED |
| Object | Kansas |
—
|
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: Kansas | Statement: [U.S. Route 400, stateWithMajorExtent, Kansas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateWithMajorExtent Context triple: [U.S. Route 400, stateWithMajorExtent, Kansas]
-
A.
majorState
Indicates that a state holds significant power, influence, or importance relative to other states within a given system or context.
-
B.
isMajorSeeWithin
Indicates that one entity is the primary or most significant location or area encompassed within the boundaries of another entity.
-
C.
stateSize
Indicates the relative or absolute physical extent or dimensions of a state, such as its area or population size.
-
D.
stateBase
Indicates that an entity serves as the foundational or primary state upon which another state or condition is defined or derived.
-
E.
isMajorRegionFor
chosen
Indicates that a region serves as a primary or significant area associated with a particular entity, activity, or phenomenon.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 12:44 p.m.