Triple
T38177357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Gough |
E1000251
|
entity |
| Predicate | hasRankInNobility |
P52082
|
FINISHED |
| Object | barony |
—
|
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: barony | Statement: [Baron Gough, hasRankInNobility, barony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankInNobility Context triple: [Baron Gough, hasRankInNobility, barony]
-
A.
hasNobleStatus
chosen
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
B.
involvedNobility
Indicates that the entities participated in or were associated with an event, action, or situation in the capacity of nobility or aristocratic status.
-
C.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
D.
parentalNobilityRank
Indicates the comparative social or noble status level held by a subject’s parent(s) within a hierarchy of nobility.
-
E.
hereditaryButNotNobleRank
Indicates that an entity holds a rank or title that is inherited across generations but does not confer noble status.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:29 p.m.