Triple
T38548736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Aire et Dax |
E925045
|
entity |
| Predicate | hasPrimaryCities |
P116685
|
FINISHED |
| Object | Aire-sur-l’Adour |
E666513
|
NE 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: Aire-sur-l’Adour | Statement: [Diocese of Aire et Dax, hasPrimaryCities, Aire-sur-l’Adour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryCities Context triple: [Diocese of Aire et Dax, hasPrimaryCities, Aire-sur-l’Adour]
-
A.
hasCentralCities
Indicates that an entity is associated with one or more cities that serve as its primary or central urban locations.
-
B.
hasPrimarySettlementsLocation
Indicates that the primary settlements of an entity are located in or associated with a specified place or geographic area.
-
C.
hasSecondaryCity
Indicates that an entity possesses or is associated with a secondary city in addition to its primary city.
-
D.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
-
E.
mainCities
chosen
Indicates that the related entities are the primary or most important cities associated with a given region, country, or area.
- F. None of above.
Provenance (4 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd4ae44881908363c1826e586564 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.