Triple
T21350606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doué-en-Anjou |
E526465
|
entity |
| Predicate | hasTroglodyteSites |
P10755
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Doué-en-Anjou, hasTroglodyteSites, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTroglodyteSites Context triple: [Doué-en-Anjou, hasTroglodyteSites, yes]
-
A.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
B.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
C.
hasCaves
chosen
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
D.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
E.
hasArchaeologicalSiteType
Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8ad31087481909d41e9d28286f04d |
completed | April 22, 2026, 11:12 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:04 p.m.