Triple
T37840546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aturri |
E943461
|
entity |
| Predicate | hasExonymForm |
P4705
|
FINISHED |
| Object | Adour |
—
|
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: Adour | Statement: [Aturri, hasExonymForm, Adour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExonymForm Context triple: [Aturri, hasExonymForm, Adour]
-
A.
hasExonym
chosen
Indicates that one entity is known by an alternative name or designation in another language or cultural context.
-
B.
hasExonymLanguageFamily
Indicates that an exonym is associated with a language family in which that exonym is used or from which it originates.
-
C.
exonymStatus
Indicates the status or classification of a name used in one language to refer to a place, people, or entity known by a different name in its own language.
-
D.
hasLanguageFormOf
Indicates that one entity is a specific linguistic form, expression, or realization of the language used by another entity.
-
E.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:19 p.m.