Triple
T14410589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Trois Villes |
E357311
|
entity |
| Predicate | mainLocations |
P3231
|
FINISHED |
| Object | three French and European cities |
—
|
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: three French and European cities | Statement: [Les Trois Villes, mainLocations, three French and European cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLocations Context triple: [Les Trois Villes, mainLocations, three French and European cities]
-
A.
mainLocation
chosen
Indicates that one entity serves as the primary or central location associated with another entity.
-
B.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
C.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
D.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
E.
mineLocation
Indicates that a specified location is the site where a particular mine (e.g., resource extraction or explosive device) is situated.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90c9b3448190aec1608836a5e913 |
completed | April 14, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69de2aa1b57881909a033eac8545c417 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.