Triple
T30511347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorkowski family |
E776434
|
entity |
| Predicate | hasRelativeOf |
P27845
|
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, hasRelativeOf, Oscar Lorkowski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeOf Context triple: [Lorkowski family, hasRelativeOf, Oscar Lorkowski]
-
A.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
B.
hasRelativeRole
chosen
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
C.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
D.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
E.
hasClosestRelativeOf
Indicates that one entity has another entity as its nearest or most closely related counterpart within a defined set or context.
- 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_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
Created at: April 29, 2026, 8:16 p.m.