Triple
T28107101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian-Slovak |
E710392
|
entity |
| Predicate | hasIdentityDimension |
P40349
|
FINISHED |
| Object | national identity |
—
|
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: national identity | Statement: [Hungarian-Slovak, hasIdentityDimension, national identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIdentityDimension Context triple: [Hungarian-Slovak, hasIdentityDimension, national identity]
-
A.
hasDimensionID
Indicates that an entity is associated with a specific dimension through its unique identifier.
-
B.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
C.
hasDimensionality
Indicates that an entity possesses a specific number of dimensions or a particular dimensional structure.
-
D.
hasIdentityComponent
chosen
Indicates that an entity includes or is associated with a specific component that contributes to or defines its identity.
-
E.
hasIndividualDimension
Indicates that an entity possesses a specific, separately identifiable dimension or measurable extent as an individual attribute.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f640c50dc88190a93952b9b87eb588 |
completed | May 2, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:09 p.m.