Triple
T26942967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skywalker family |
E678566
|
entity |
| Predicate | lineageBeginsWith |
P115355
|
FINISHED |
| Object | Shmi Skywalker Lars |
—
|
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: Shmi Skywalker Lars | Statement: [Skywalker family, lineageBeginsWith, Shmi Skywalker Lars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineageBeginsWith Context triple: [Skywalker family, lineageBeginsWith, Shmi Skywalker Lars]
-
A.
lineageSystem
Indicates a hierarchical ancestry or descent relationship that traces how entities are derived from or originate through one another within a system.
-
B.
titleLineageStart
Indicates the point in time or event at which a particular title or rank first begins within a lineage or succession.
-
C.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
-
D.
sourceOfLineageFor
chosen
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
E.
lineageConcept
Indicates a conceptual or abstract relationship of lineage, such as ancestry or descent, between entities.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 6:19 a.m.