Triple
T34060424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krzemieniec estates |
E873477
|
entity |
| Predicate | belongedToEstateMagnateClass |
P137842
|
FINISHED |
| Object | Polish 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: Polish nobility | Statement: [Krzemieniec estates, belongedToEstateMagnateClass, Polish nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongedToEstateMagnateClass Context triple: [Krzemieniec estates, belongedToEstateMagnateClass, Polish nobility]
-
A.
aristocratic estate
chosen
Indicates a relationship in which a property or landholding is owned, controlled, or associated with members of the aristocracy or nobility.
-
B.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
C.
hadEstates
Indicates that an entity possessed or owned one or more estates (properties or landholdings).
-
D.
hasRelativeInAristocracy
Indicates that an entity has at least one relative who belongs to the aristocracy or noble class.
-
E.
hadRulingClass
Indicates that a particular group or class held dominant political, economic, or social power over a society or entity.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: May 1, 2026, 1:52 a.m.