Triple
T36030211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huveaune River |
E1042237
|
entity |
| Predicate | historicalMouthLocatedIn |
P1008
|
FINISHED |
| Object | Mediterranean Sea |
—
|
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: Mediterranean Sea | Statement: [Huveaune River, historicalMouthLocatedIn, Mediterranean Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMouthLocatedIn Context triple: [Huveaune River, historicalMouthLocatedIn, Mediterranean Sea]
-
A.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
B.
mouthOf
chosen
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
C.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
D.
historicallyLocatedOutside
Indicates that an entity was historically situated beyond the boundaries or limits of another specified place or region.
-
E.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00d76d0e0881908d83a8dcce511167 |
completed | May 10, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a00d711805881909a94cfd1f25fb331 |
completed | May 10, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.