Triple
T33052125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buccleuch branch |
E845753
|
entity |
| Predicate | historicallyHoldsRank |
P129060
|
FINISHED |
| Object | ducal |
—
|
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: ducal | Statement: [Buccleuch branch, historicallyHoldsRank, ducal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyHoldsRank Context triple: [Buccleuch branch, historicallyHoldsRank, ducal]
-
A.
rankHistory
chosen
Indicates the historical sequence of ranks or positions an entity has held over time.
-
B.
typicallyHoldsRank
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
C.
nationalRankingHistorical
Indicates the historical position or level an entity held within a national ranking over time.
-
D.
traditionallyRankedAfter
Indicates that one entity is customarily ordered or placed after another according to established tradition or conventional ranking.
-
E.
lastHolderRank
Indicates the rank or position held by the most recent entity that possessed or held a given item, title, or role.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
Created at: May 1, 2026, 1:24 a.m.