Triple
T32113394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master of Buckland |
E820174
|
entity |
| Predicate | equivalentInShire |
P28033
|
FINISHED |
| Object | regional lord |
—
|
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: regional lord | Statement: [Master of Buckland, equivalentInShire, regional lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentInShire Context triple: [Master of Buckland, equivalentInShire, regional lord]
-
A.
equivalentIn
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
-
B.
hasExactImperialEquivalent
Indicates that one measurement or quantity has a directly corresponding and precisely equal value in the imperial system.
-
C.
isShireSeatOf
Indicates that a location serves as the administrative center or county town (shire seat) for a given shire or county.
-
D.
thaatEquivalentInHindustani
Indicates that two musical elements are equivalent or correspond to the same thaat (parent scale) within the Hindustani music system.
-
E.
equivalentTitleInEngland
chosen
Indicates that one title corresponds to an equivalent or matching title within the context of England’s system of titles.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 12:27 a.m.