Triple
T15568157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ansião |
E374168
|
entity |
| Predicate | roadConnection |
P385
|
FINISHED |
| Object | IC8 |
E1133960
|
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: IC8 | Statement: [Ansião, roadConnection, IC8]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IC8 Context triple: [Ansião, roadConnection, IC8]
-
A.
IC8
chosen
IC8 is a major Portuguese roadway that serves as an important regional connector in central Portugal.
-
B.
IR8
IR8 is a high-yielding semi-dwarf rice variety developed during the Green Revolution that significantly increased rice production worldwide.
-
C.
IC
IC was the stock ticker symbol used by the historic Illinois Central Railroad, a major U.S. railroad that played a key role in Midwestern and Southern rail transport.
-
D.
IC
IC is a common abbreviation for Iowa City, a university-centered community best known as the home of the University of Iowa and its renowned Writers' Workshop.
-
E.
IC
IC is a category of long-distance passenger trains in Poland, operated by PKP Intercity and offering intercity connections between major cities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04dde90b081908284d9258d4462e3 |
completed | April 16, 2026, 2:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff56c231e0819083d6032eb21114b2 |
completed | May 9, 2026, 3:46 p.m. |
Created at: April 10, 2026, 4:10 a.m.