Triple
T10818801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boone County, Indiana |
E255304
|
entity |
| Predicate | hasISOCode |
P189
|
FINISHED |
| Object | US-IN |
E174641
|
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: US-IN | Statement: [Boone County, Indiana, hasISOCode, US-IN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: US-IN Context triple: [Boone County, Indiana, hasISOCode, US-IN]
-
A.
US-IN
chosen
US-IN is the ISO 3166-2 code designating the U.S. state of Indiana.
-
B.
US
US is the commonly used abbreviation for the University of Szczecin, a public higher education institution in Szczecin, Poland.
-
C.
US
US is the IATA airline designator code assigned to the former American airline US Airways.
-
D.
US
The US, or United States, is a federal republic in North America comprising 50 states and known as one of the world's largest economic and military powers.
-
E.
US
The US, or United States, is a large federal republic in North America composed of 50 states and known as one of the world's most influential economic and political powers.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344866f88190be4addb7c8020fce |
completed | April 9, 2026, 5:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de8569178481909474e939a3e4c217 |
completed | April 14, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:18 p.m.