Triple
T38043111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Nassau-Hadamar |
E949542
|
entity |
| Predicate | hasNobleRankHigherThan |
P31174
|
FINISHED |
| Object | Count of Nassau-Hadamar |
E218120
|
NE 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: Count of Nassau-Hadamar | Statement: [Prince of Nassau-Hadamar, hasNobleRankHigherThan, Count of Nassau-Hadamar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobleRankHigherThan Context triple: [Prince of Nassau-Hadamar, hasNobleRankHigherThan, Count of Nassau-Hadamar]
-
A.
nobleRankAbove
chosen
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
B.
nobleRankLowerThan
Indicates that one entity holds a noble rank that is lower in hierarchy than the noble rank held by another entity.
-
C.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
D.
nobleRankOf
Indicates that one entity holds a specific noble title or rank within a hierarchical nobility system.
-
E.
hasNoblePrecedence
Indicates that one entity holds a higher rank or priority in a formal noble or aristocratic order than another entity.
- F. None of above.
Provenance (4 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d30d0908190aa8f79c12876dae2 |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.