Triple
T12819465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivanova |
E306489
|
entity |
| Predicate | indicatesLineageFrom |
P77522
|
FINISHED |
| Object | a person named Ivan |
—
|
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: a person named Ivan | Statement: [Ivanova, indicatesLineageFrom, a person named Ivan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesLineageFrom Context triple: [Ivanova, indicatesLineageFrom, a person named Ivan]
-
A.
hasLineageDocumentedIn
Indicates that the lineage or ancestry of an entity is recorded or evidenced in a specified document or source.
-
B.
hasLineageStructure
Indicates that an entity participates in or exhibits a hierarchical ancestry or lineage-based structural relationship to other entities.
-
C.
isLineageType
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
-
D.
hasLineageMember
chosen
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
-
E.
hasNotableLineageFor
Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage in relation to another entity.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e9e5a2481908921d097df541db8 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d964100f7481909a197396003d4a71 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.