Triple
T3106024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Save |
E64831
|
entity |
| Predicate | hasMouthPositionRelativeToCity |
P45963
|
FINISHED |
| Object | northwest of Toulouse |
—
|
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: northwest of Toulouse | Statement: [Save, hasMouthPositionRelativeToCity, northwest of Toulouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMouthPositionRelativeToCity Context triple: [Save, hasMouthPositionRelativeToCity, northwest of Toulouse]
-
A.
mouthLocatedInAdministrativeEntity
Indicates that the place where a river ends (its mouth) is situated within a specific administrative region or jurisdiction.
-
B.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
C.
cityAtMouth
Indicates that a city is located at or very near the mouth (outlet) of a river.
-
D.
representedCity
Indicates that an entity serves as the official representative or proxy for a particular city.
-
E.
hasTargetCity
Indicates that something is directed toward, intended for, or specifically associated with a particular city as its target.
- F. None of above. chosen
Provenance (4 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29beff08190b6e1eb6b0608d0eb |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.