Triple
T28066778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Mackintosh |
E709274
|
entity |
| Predicate | feudalTerritory |
P87619
|
FINISHED |
| Object | Moy |
—
|
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: Moy | Statement: [Clan Mackintosh, feudalTerritory, Moy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feudalTerritory Context triple: [Clan Mackintosh, feudalTerritory, Moy]
-
A.
feudalCenter
Indicates that a location serves as the primary seat of authority, administration, or power within a feudal system.
-
B.
formerFiefOf
chosen
Indicates that a territory or domain was previously under the control or jurisdiction of a specified lord, ruler, or political entity as a fief.
-
C.
feudalType
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
-
D.
feudName
Indicates a named rivalry or ongoing conflict that exists between entities.
-
E.
feudType
Indicates the specific kind or category of ongoing conflict or long-standing hostility that exists between entities.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6401c365c8190bf95e0e5c1f94021 |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:43 p.m.