Triple
T37903288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Illinois |
E945476
|
entity |
| Predicate | includesPartsOfPresentDay |
P3475
|
FINISHED |
| Object | Illinois |
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 | Statement: [Spanish Illinois, includesPartsOfPresentDay, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPartsOfPresentDay Context triple: [Spanish Illinois, includesPartsOfPresentDay, Illinois]
-
A.
partOfPresentDay
chosen
Indicates that one entity is a component, region, or subset of what constitutes the other entity in its current, modern-day form.
-
B.
usedInPresentDayCountry
Indicates that something is currently utilized or occurs within the boundaries of a specified modern-day country.
-
C.
presentDayIncludes
Indicates that the current day in a given calendar or time context encompasses or contains a specified time, date, or event.
-
D.
contemporaryPresenceIn
Indicates that an entity exists or is present in a particular place, context, or timeframe at the same time as another specified reference point or entity.
-
E.
traversesPresentDay
Indicates that one entity currently passes through, crosses, or extends across another entity in the present day.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4117ea06dc8190a52ffdd10a133aa6 |
completed | June 28, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.