Triple
T17292037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Nassau-Weilburg |
E419806
|
entity |
| Predicate | heldByNobilityOf |
P64068
|
FINISHED |
| Object | German 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: German nobility | Statement: [Count of Nassau-Weilburg, heldByNobilityOf, German nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByNobilityOf Context triple: [Count of Nassau-Weilburg, heldByNobilityOf, German nobility]
-
A.
heldFief
Indicates that one entity possessed or controlled a fief (a feudal estate or tenure) from another entity.
-
B.
usedByNobility
chosen
Indicates that something is employed, possessed, or utilized specifically by members of the nobility.
-
C.
aristocraticTitleHeldFrom
Indicates the time period or starting point from which an aristocratic title was held by an entity.
-
D.
heldUnderDynasty
Indicates that an entity’s position, title, or authority was exercised during the rule of a specific dynasty.
-
E.
heldByHeirApparentOf
Indicates that something is possessed, controlled, or occupied by the heir apparent of a particular person, title, or position.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4378438508190924f732ad748b4d0 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.