Triple
T38235324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby Lorrain |
E1013604
|
entity |
| Predicate | locatedInSportsRegion |
P96807
|
FINISHED |
| Object | Grand Est |
E21143
|
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: Grand Est | Statement: [Derby Lorrain, locatedInSportsRegion, Grand Est]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSportsRegion Context triple: [Derby Lorrain, locatedInSportsRegion, Grand Est]
-
A.
basedInSportRegion
Indicates that an entity’s primary sports-related activities or affiliations are located within a specified geographic region.
-
B.
locationOfSport
Indicates the place where a particular sport is played, practiced, or held.
-
C.
isInSportCountry
Indicates that an entity is located in or associated with the country where a particular sport activity, event, or organization takes place.
-
D.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
E.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41cc91d3a881909885cd0dda1e6f54 |
completed | June 29, 2026, 1:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.