Triple
T32004353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raider |
E817219
|
entity |
| Predicate | locationOfOrganizationRepresented |
P203705
|
FINISHED |
| Object | Illinois (U.S. state) |
E13723
|
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: Illinois (U.S. state) | Statement: [Raider, locationOfOrganizationRepresented, Illinois (U.S. state)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfOrganizationRepresented Context triple: [Raider, locationOfOrganizationRepresented, Illinois (U.S. state)]
-
A.
organizationLocatedAt
Indicates that an organization is situated or based at a specific geographic location or address.
-
B.
locationOfRepresentation
chosen
Indicates that one entity is the place or site where another entity is depicted, displayed, or represented.
-
C.
locationOfGoverningBody
Indicates the place where a governing body is based or carries out its official functions.
-
D.
agencyLocatedIn
Indicates that an agency is situated or based within a specific geographic or administrative location.
-
E.
currentRepresentativeOffice
Indicates that an entity currently serves as the official representative office for another entity (such as a government, organization, or company).
- F. None of above.
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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01f4d954e08190aff3756955212d67 |
completed | May 11, 2026, 3:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb16342808190809e1afff5d2971a |
completed | June 14, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_6a01edadb9248190be592287530740a5 |
completed | May 11, 2026, 2:54 p.m. |
Created at: May 1, 2026, 12:14 a.m.