Triple
T5158119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juvisy-sur-Orge |
E116363
|
entity |
| Predicate | isCommuneStatus |
P37705
|
FINISHED |
| Object | commune |
—
|
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: commune | Statement: [Juvisy-sur-Orge, isCommuneStatus, commune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommuneStatus Context triple: [Juvisy-sur-Orge, isCommuneStatus, commune]
-
A.
hasCommune
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
B.
isMunicipalStatus
chosen
Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
-
C.
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).
-
D.
singleCommuneProvince
Indicates that a province contains exactly one commune within its administrative boundaries.
-
E.
belongsToIntercommunality
Indicates that an entity is a member of, or administratively attached to, a specific intercommunal structure or grouping.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.