Triple
T28468367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Thurso |
E720360
|
entity |
| Predicate | belongsToNobleHouse |
P182094
|
FINISHED |
| Object | House of Sinclair |
—
|
NE NERFINISHED |
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: House of Sinclair | Statement: [Viscount Thurso, belongsToNobleHouse, House of Sinclair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToNobleHouse Context triple: [Viscount Thurso, belongsToNobleHouse, House of Sinclair]
-
A.
associatedNobleFamily
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
B.
noble house
chosen
Indicates a hierarchical familial or dynastic relationship in which individuals belong to a recognized aristocratic lineage or ruling family.
-
C.
hasNobleHouseOrigin
Indicates that an entity originates from, or is ancestrally associated with, a particular noble house.
-
D.
usedByNobleFamily
Indicates that something is employed, possessed, or otherwise utilized by a noble family.
-
E.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or title.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 28, 2026, 2:46 a.m.