Triple
T34583401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lycée de Ville-d'Avray |
E887971
|
entity |
| Predicate | communeServed |
P104901
|
FINISHED |
| Object | Ville-d'Avray |
—
|
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: Ville-d'Avray | Statement: [Lycée de Ville-d'Avray, communeServed, Ville-d'Avray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communeServed Context triple: [Lycée de Ville-d'Avray, communeServed, Ville-d'Avray]
-
A.
servesCommune
Indicates that an entity provides services or functions in support of a particular commune or local municipality.
-
B.
hasCommune
Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
-
C.
townServed
chosen
Indicates that a given service, facility, or infrastructure serves or provides coverage to a particular town.
-
D.
isCommune
Indicates that an entity functions as or has the status of a commune, typically a local administrative or municipal unit.
-
E.
servedCommunitiesIncluding
Indicates that an entity provided services or benefits to a set of communities that includes, but may not be limited to, the specified communities.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f73397e5488190a9cdce98a0ac0383 |
completed | May 3, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69f732f3ad248190b4bcbf589d000f0d |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 2:03 a.m.