Triple
T35156568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankee Nord Marseille |
E1015137
|
entity |
| Predicate | cityOfClubSupported |
P164554
|
FINISHED |
| Object | Marseille |
—
|
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: Marseille | Statement: [Yankee Nord Marseille, cityOfClubSupported, Marseille]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfClubSupported Context triple: [Yankee Nord Marseille, cityOfClubSupported, Marseille]
-
A.
homeCityOfClubSupported
chosen
Indicates that a particular city is the home city of the sports club that an entity supports.
-
B.
isLocatedInCityWithClub
Indicates that an entity is situated in a city that has at least one (sports or similar) club based there.
-
C.
participatingClubsFromCity
Indicates that the clubs involved in an event or activity originate from or are based in a specified city.
-
D.
supportsClubRegion
Indicates that an entity provides backing, resources, or endorsement to a club associated with a particular geographic region.
-
E.
usedByClubFromCity
Indicates that something (such as a facility, stadium, or resource) is utilized by a sports club that is based in a particular 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.