Triple
T31712739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ta’oma’ |
E809371
|
entity |
| Predicate | hasDescendantFormInLanguage |
P106922
|
FINISHED |
| Object | Thomas in English |
—
|
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: Thomas in English | Statement: [Ta’oma’, hasDescendantFormInLanguage, Thomas in English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDescendantFormInLanguage Context triple: [Ta’oma’, hasDescendantFormInLanguage, Thomas in English]
-
A.
hasLaterFormLanguage
Indicates that one language has a subsequent or later-developed form or variant in another language.
-
B.
hasLanguageFormOf
chosen
Indicates that one entity is a specific linguistic form, expression, or realization of the language used by another entity.
-
C.
hasSubLanguage
Indicates that one language is a subset, variant, or specialized form of another language.
-
D.
hasSuccessorLanguageInRegion
Indicates that one language is followed or replaced by another language within a specific geographic region.
-
E.
hasRelatedLanguage
Indicates that one language is related to another through shared linguistic origins, features, or classification.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 30, 2026, 11:16 p.m.