Triple
T30511346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorkowski family |
E776434
|
entity |
| Predicate | sharesCommonLineage |
P117069
|
FINISHED |
| Object | Oscar Lorkowski |
—
|
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: Oscar Lorkowski | Statement: [Lorkowski family, sharesCommonLineage, Oscar Lorkowski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCommonLineage Context triple: [Lorkowski family, sharesCommonLineage, Oscar Lorkowski]
-
A.
sharesCommonAncestorWith
Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
-
B.
sharesParentsWith
Indicates that two entities have the same parents, making them siblings or otherwise sharing identical parentage.
-
C.
sharesFamilyLineageWith
chosen
Indicates that two entities descend from the same family line or share common ancestors.
-
D.
sharesTrunkLineWith
Indicates that two entities are connected to or use the same primary communication or utility trunk line.
-
E.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 29, 2026, 8:16 p.m.