Triple
T29386535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tófa |
E745268
|
entity |
| Predicate | hasDescendantName |
P193191
|
FINISHED |
| Object | Tove |
—
|
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: Tove | Statement: [Tófa, hasDescendantName, Tove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDescendantName Context triple: [Tófa, hasDescendantName, Tove]
-
A.
hasDescendantForm
Indicates that one entity is a later, derived, or evolved form that descends from another entity.
-
B.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
C.
refersToAncestorNamed
Indicates that an entity refers to an ancestor specifically identified by a given name.
-
D.
hasDescendantRegion
Indicates that one region includes or gives rise to another region that is hierarchically below it in a geographic or administrative structure.
-
E.
hasDescendantsType
Indicates that an entity has descendants belonging to a specified type or category.
- F. None of above. chosen
Provenance (4 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
| PDg | Predicate description generation | batch_69fd3a6905b88190ae12b43576f4cc63 |
completed | May 8, 2026, 1:20 a.m. |
Created at: April 28, 2026, 2:39 p.m.