Triple
T27524748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panina |
E694802
|
entity |
| Predicate | withinLineage |
P152701
|
FINISHED |
| Object | human lineage |
—
|
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: human lineage | Statement: [Panina, withinLineage, human lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinLineage Context triple: [Panina, withinLineage, human lineage]
-
A.
impliesLineage
Indicates that one entity is inferred to be ancestrally or genealogically derived from another.
-
B.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
C.
isLineageType
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
-
D.
hasLineageMember
Indicates that one entity is a member or descendant within the lineage or ancestral line of another entity.
-
E.
hasLineageConnectionTo
chosen
Indicates a genealogical or ancestral relationship exists between two entities, such as descent, shared ancestry, or familial lineage.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:23 p.m.