Triple
T13531892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Inhabitants |
E323152
|
entity |
| Predicate | hasEnglishFormOf |
P106922
|
FINISHED |
| Object | Les Habitants |
—
|
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: Les Habitants | Statement: [The Inhabitants, hasEnglishFormOf, Les Habitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnglishFormOf Context triple: [The Inhabitants, hasEnglishFormOf, Les Habitants]
-
A.
hasLanguageFormOf
chosen
Indicates that one entity is a specific linguistic form, expression, or realization of the language used by another entity.
-
B.
hasEnglishName
Indicates that an entity is associated with a name expressed in the English language.
-
C.
hasEnglishGloss
Indicates that one entity serves as the English-language gloss or explanatory translation for the other entity.
-
D.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
-
E.
hasEnglishNameMeaning
Indicates that an entity is associated with an English-language name along with the meaning or semantic interpretation of that name.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbb34548190a6b44faa48125cd4 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.