Triple
T26876023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois lies generally northwest of Kentucky |
E676750
|
entity |
| Predicate | describesLocationOf |
P3024
|
FINISHED |
| Object | Illinois |
—
|
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: Illinois | Statement: [Illinois lies generally northwest of Kentucky, describesLocationOf, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesLocationOf Context triple: [Illinois lies generally northwest of Kentucky, describesLocationOf, Illinois]
-
A.
locationDescription
chosen
Indicates a textual description that specifies or characterizes the location of an entity.
-
B.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
E.
introductionLocation
Indicates the place or setting where an introduction or initial presentation of something or someone occurs.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 5:36 a.m.