Triple
T25182382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esas Holding |
E630617
|
entity |
| Predicate | notableShareholderFamily |
P54686
|
FINISHED |
| Object | Sabancı family |
E1665296
|
NE 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: Sabancı family | Statement: [Esas Holding, notableShareholderFamily, Sabancı family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableShareholderFamily Context triple: [Esas Holding, notableShareholderFamily, Sabancı family]
-
A.
notableHolderFamily
chosen
Indicates that a particular family is notably associated with holding, possessing, or being custodians of the referenced entity.
-
B.
notableFamilyFor
Indicates that a family is particularly recognized or distinguished for a specific person, achievement, role, or characteristic.
-
C.
notableFamilyIn
Indicates that a person is notably associated with or belongs to a particular family within a given place or context.
-
D.
notableLeaderFamily
Indicates that a person belongs to the family of a notable or prominent leader.
-
E.
notableFamilyNameOf
Indicates that a particular family name is notably or prominently associated with a given person or family entity.
- F. None of above.
Provenance (4 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1075c5b7cc8190b2c9c6fea539fd28 |
completed | May 22, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 21, 2026, 12:36 p.m.