Triple
T21101041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wei |
E519903
|
entity |
| Predicate | canBeMultipleLineages |
P65475
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Wei, canBeMultipleLineages, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeMultipleLineages Context triple: [Wei, canBeMultipleLineages, true]
-
A.
hasLineageStructure
Indicates that an entity participates in or exhibits a hierarchical ancestry or lineage-based structural relationship to other entities.
-
B.
hasMultipleGenealogies
chosen
Indicates that an entity is associated with more than one distinct genealogical lineage or family tree.
-
C.
hasNotableLineageFor
Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage in relation to another entity.
-
D.
hasLineageStatus
Indicates the lineage or ancestry classification assigned to an entity, such as whether and how it descends from or is derived from another.
-
E.
includesMulticellularLineages
Indicates that the subject encompasses or contains one or more lineages composed of multicellular organisms.
- 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b5e16cc81908257ccf8c9a59117 |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.