Triple
T29339593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lukasz |
E744000
|
entity |
| Predicate | isRelatedNameInFamily |
P3889
|
FINISHED |
| Object | Lukas |
—
|
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: Lukas | Statement: [Lukasz, isRelatedNameInFamily, Lukas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedNameInFamily Context triple: [Lukasz, isRelatedNameInFamily, Lukas]
-
A.
isRelatedName
chosen
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
B.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
C.
isPaternalFamilyNameOf
Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
-
D.
belongsToFamilyCommonName
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
E.
isOriginalFamilyNameOf
Indicates that a given family name is the original or birth surname of a person, from which any later or changed surnames may have derived.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f669261f588190aa20417cfee752e4 |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 1:33 p.m.