Triple
T3827588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade de la Mosson |
E88726
|
entity |
| Predicate | floodDamageConsequence |
P50010
|
FINISHED |
| Object | temporary relocation of Montpellier HSC home matches |
—
|
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: temporary relocation of Montpellier HSC home matches | Statement: [Stade de la Mosson, floodDamageConsequence, temporary relocation of Montpellier HSC home matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floodDamageConsequence Context triple: [Stade de la Mosson, floodDamageConsequence, temporary relocation of Montpellier HSC home matches]
-
A.
floodConsequence
chosen
Indicates the resulting effects, outcomes, or impacts that occur as a consequence of a flood event.
-
B.
floodCause
Indicates that one entity is the cause or source of a flood affecting another entity or area.
-
C.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
D.
impactOfDrainage
Indicates the effect or consequences that a drainage system or drainage activity has on a particular target or environment.
-
E.
hasFloodRisk
Indicates that an entity is exposed to a potential or expected risk of flooding under certain conditions.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8459f881908a2c91bb07e381ef |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.