Triple
T9840996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Eagle |
E239223
|
entity |
| Predicate | accountLanguage |
P18209
|
FINISHED |
| Object | English (through an interpreter or editor) |
—
|
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: English (through an interpreter or editor) | Statement: [Big Eagle, accountLanguage, English (through an interpreter or editor)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accountLanguage Context triple: [Big Eagle, accountLanguage, English (through an interpreter or editor)]
-
A.
identityLanguage
Indicates that two language entities are identical or represent the same language.
-
B.
parentLanguage
Indicates that one language is the ancestral or source language from which another language is derived or historically developed.
-
C.
eligibleLanguage
Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
-
D.
serviceBrandLanguage
Indicates the language or languages in which a service brand communicates or is presented.
-
E.
languageUse
chosen
Indicates the language or languages an entity uses for communication, expression, or interaction.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34c920c81909b56ed9936b15f9b |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.