Triple
T31712752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ta’oma’ |
E809371
|
entity |
| Predicate | hasDiminutiveViaDescendants |
P456
|
FINISHED |
| Object | Tommy |
—
|
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: Tommy | Statement: [Ta’oma’, hasDiminutiveViaDescendants, Tommy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiminutiveViaDescendants Context triple: [Ta’oma’, hasDiminutiveViaDescendants, Tommy]
-
A.
hasDiminutive
chosen
Indicates that one entity is a diminutive form or smaller/affectionate variant of another entity.
-
B.
hasPatronymicDerivative
Indicates that one name or term is derived from another by forming a patronymic, typically expressing descent or lineage from a person.
-
C.
isShortenedVariantOf
Indicates that one form of an expression is a shortened or abbreviated version of another, longer form.
-
D.
hasSubAppellation
Indicates that one appellation (name or title) is a more specific or subordinate form of another appellation.
-
E.
hasDescendantName
Indicates that an entity has a descendant whose name matches a specified value or identifier.
- 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_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 30, 2026, 11:16 p.m.