Triple
T25704096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Country of the Houyhnhnms |
E644539
|
entity |
| Predicate | languageUsedByInhabitants |
P115774
|
FINISHED |
| Object | Houyhnhnm language |
—
|
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: Houyhnhnm language | Statement: [Country of the Houyhnhnms, languageUsedByInhabitants, Houyhnhnm language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedByInhabitants Context triple: [Country of the Houyhnhnms, languageUsedByInhabitants, Houyhnhnm language]
-
A.
hasLanguageInhabitants
Indicates that a particular language is spoken or used by the inhabitants of a specified place or region.
-
B.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
C.
languageUsedInLocality
chosen
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
D.
languageOfVocalization
Indicates the language in which a vocalization (such as speech or singing) is produced.
-
E.
languageOfEnvironment
Indicates the language predominantly used or present in a given environment or context.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 21, 2026, 9:01 p.m.