Triple
T32838130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zrt. |
E839891
|
entity |
| Predicate | companyTypeFamily |
P191026
|
FINISHED |
| Object | részvénytársaság |
—
|
LITERAL 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: részvénytársaság | Statement: [Zrt., companyTypeFamily, részvénytársaság]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyTypeFamily Context triple: [Zrt., companyTypeFamily, részvénytársaság]
-
A.
serviceDesignationFamily
Indicates that one service designation is part of the same family or grouping as another, reflecting a shared classification or closely related category.
-
B.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
-
C.
organizationalFamily
Indicates that one organization is related to another as part of the same organizational family, such as parent, subsidiary, or affiliate within a shared corporate or institutional structure.
-
D.
coreFamily
Indicates that one entity belongs to the other’s immediate (nuclear) family, such as parent, child, or sibling.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- F. None of above. chosen
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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: May 1, 2026, 1:16 a.m.