Triple
T30570517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuruc forces |
E778109
|
entity |
| Predicate | hasSocialComposition |
P8216
|
FINISHED |
| Object | nobility |
—
|
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: nobility | Statement: [Kuruc forces, hasSocialComposition, nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialComposition Context triple: [Kuruc forces, hasSocialComposition, nobility]
-
A.
hasSocialStructure
chosen
Indicates that an entity exhibits an organized pattern of social relationships or hierarchy among its members.
-
B.
hasSocialDimension
Indicates that the relationship, attribute, or phenomenon involves social aspects, interactions, or implications among individuals or groups.
-
C.
hasEthnicOrNationalComposition
Indicates that an entity is characterized by a particular ethnic or national group composition.
-
D.
hasSocialGroup
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
-
E.
hasSocialIdentity
Indicates that an entity possesses or is associated with a particular social identity, such as a role, group membership, or socially recognized status.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 8:22 p.m.