Triple
T25582394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois Route 5 |
E641283
|
entity |
| Predicate | isPartlyKnownAs |
P172753
|
FINISHED |
| Object | Illinois Route 5 (partly) |
—
|
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 Route 5 (partly) | Statement: [Illinois Route 5, isPartlyKnownAs, Illinois Route 5 (partly)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartlyKnownAs Context triple: [Illinois Route 5, isPartlyKnownAs, Illinois Route 5 (partly)]
-
A.
alsoKnownAs
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
B.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
C.
isWidelyKnownAs
Indicates that an entity is commonly referred to or recognized by a particular name or label by a broad audience.
-
D.
knewAs
Indicates that one entity was acquainted with or recognized another entity under a particular identity, name, or role.
-
E.
knowsAs
Indicates that one entity recognizes or refers to another entity by a particular name, alias, or identifier.
- F. None of above. chosen
Provenance (4 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 21, 2026, 4:13 p.m.