Triple
T38318948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Theresa |
E1036603
|
entity |
| Predicate | nobleRankRequirement |
P121828
|
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: [Order of Theresa, nobleRankRequirement, nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleRankRequirement Context triple: [Order of Theresa, nobleRankRequirement, nobility]
-
A.
nobleRankRequired
chosen
Indicates that a certain minimum noble rank or title is required for the related action, status, or relationship to apply.
-
B.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
C.
nobleRankLowerThan
Indicates that one entity holds a noble rank that is lower in hierarchy than the noble rank held by another entity.
-
D.
nobleRankScope
Indicates the scope or domain within which a particular noble rank is valid, recognized, or applies.
-
E.
nobleRankOf
Indicates that one entity holds a specific noble title or rank within a hierarchical nobility system.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.