Triple
T5170198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian nobility |
E116657
|
entity |
| Predicate | socialPrivilege |
P27958
|
FINISHED |
| Object | use of noble titles |
—
|
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: use of noble titles | Statement: [Hungarian nobility, socialPrivilege, use of noble titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialPrivilege Context triple: [Hungarian nobility, socialPrivilege, use of noble titles]
-
A.
socialClassAspiration
Indicates a desire or intention by one entity to attain a higher or different social class or status than its current one.
-
B.
socialClassSystem
Indicates a hierarchical organization of people into social classes based on status, power, or economic position.
-
C.
socialPosition
Indicates the relative social status, rank, or standing one entity holds within a social hierarchy or structure in relation to others.
-
D.
socialClassRepresented
Indicates that one entity portrays, embodies, or stands in for the social class or socioeconomic group associated with another entity.
-
E.
associatedWithSocialClass
chosen
Indicates a relationship in which an entity is linked or connected to a particular social class or socioeconomic stratum.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd794f44248190a3a90c92208104a7 |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.