Triple
T36727137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champagne Châlons-Reims Basket |
E907224
|
entity |
| Predicate | homeCity1 |
P150859
|
FINISHED |
| Object | Châlons-en-Champagne |
—
|
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: Châlons-en-Champagne | Statement: [Champagne Châlons-Reims Basket, homeCity1, Châlons-en-Champagne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCity1 Context triple: [Champagne Châlons-Reims Basket, homeCity1, Châlons-en-Champagne]
-
A.
homeCityOf
chosen
Indicates that a particular city is the primary place of residence or origin for a given person or organization.
-
B.
homeCityInStory
Indicates that a specified city serves as a character’s home city within the context of a particular story.
-
C.
homeCityInBackstory
Indicates that an entity has a specified city as its home city within its narrative or character backstory.
-
D.
homeCityMetropolitanArea
Indicates that a specified city serves as the primary metropolitan area associated with a given entity’s home location.
-
E.
homeCityRole
Indicates that an entity holds or held a specific role, position, or function associated with their home city.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.