Triple
T16293328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Rouen |
E395580
|
entity |
| Predicate | regionLeagueContext |
P14506
|
FINISHED |
| Object | Normandy football |
—
|
LITERAL 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: Normandy football | Statement: [FC Rouen, regionLeagueContext, Normandy football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionLeagueContext Context triple: [FC Rouen, regionLeagueContext, Normandy football]
-
A.
regionLeague
chosen
Indicates a relationship where a specific region is associated with, belongs to, or is governed by a particular league or league-level organization.
-
B.
leagueContext
Indicates the broader league or competition setting within which the relationship or action takes place.
-
C.
locationLeague
Indicates that an entity (such as a sports team or club) is associated with or participates in a particular league.
-
D.
countryLeagueRepresents
Indicates that a particular league serves as the official representative or embodiment of a country in a given sport or competitive context.
-
E.
beganInLeagueContext
Indicates that an entity’s activity, participation, or career started specifically within the context of a particular league or league-based competition.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2aee6881909fd28547f135427c |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.