Triple
T35488024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US-NE |
E1025650
|
entity |
| Predicate | assignedToSubdivision |
P66180
|
FINISHED |
| Object | state of Nebraska |
—
|
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: state of Nebraska | Statement: [US-NE, assignedToSubdivision, state of Nebraska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedToSubdivision Context triple: [US-NE, assignedToSubdivision, state of Nebraska]
-
A.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
B.
assignedToArea
Indicates that something has been allocated or designated to a specific area or region.
-
C.
associatedWithSubdivision
chosen
Indicates that one entity has a connection or linkage to a specific administrative or organizational subdivision.
-
D.
assignedToUnit
Indicates that an entity (such as a person, resource, or task) is allocated or designated to a specific unit or organizational subdivision.
-
E.
assignedAs
Indicates that one entity is designated or appointed to perform a specific role, task, or function in relation to another entity.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.