Triple
T15259824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paillon |
E364744
|
entity |
| Predicate | mouthLocationRelative |
P45963
|
FINISHED |
| Object | east of Nice city center |
—
|
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: east of Nice city center | Statement: [Paillon, mouthLocationRelative, east of Nice city center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthLocationRelative Context triple: [Paillon, mouthLocationRelative, east of Nice city center]
-
A.
mouthNear
Indicates that one entity’s mouth is positioned close to another entity or object in space.
-
B.
mouthDirection
Indicates the orientation or facing direction of a mouth relative to a reference frame or another object.
-
C.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
-
D.
fromMouth
Indicates that something originates from or is emitted out of a mouth.
-
E.
hasMouthPositionRelativeToCity
chosen
Indicates the spatial position of a river’s mouth in relation to a specified 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084d11148190919eef8e55569bb9 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.