Triple
T29668523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port-Marly |
E750600
|
entity |
| Predicate | isRiversideCommune |
P50435
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Port-Marly, isRiversideCommune, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRiversideCommune Context triple: [Port-Marly, isRiversideCommune, true]
-
A.
isRuralCommune
Indicates that the subject entity is classified as a rural commune, i.e., an administrative unit characterized by predominantly non-urban, countryside or village-based settlement.
-
B.
hasCommune
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
C.
isRiverside
chosen
Indicates that one entity is located beside or along the bank of a river in relation to another entity.
-
D.
isUrbanCommuneOf
Indicates that one entity is an urban commune that administratively belongs to or is part of another entity (typically a higher-level territorial unit).
-
E.
isRiversideRangeOf
Indicates that something is a range or stretch of land that lies along the side of a river.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f671c5d3308190b78b458b37ee5e47 |
completed | May 2, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:02 p.m.