Triple
T15025939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maclean of Torloisk |
E378213
|
entity |
| Predicate | hasCadetRelationshipTo |
P2906
|
FINISHED |
| Object | Chief of Clan Maclean |
—
|
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: Chief of Clan Maclean | Statement: [Maclean of Torloisk, hasCadetRelationshipTo, Chief of Clan Maclean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCadetRelationshipTo Context triple: [Maclean of Torloisk, hasCadetRelationshipTo, Chief of Clan Maclean]
-
A.
hasCadetType
Indicates that an entity is associated with or classified under a specific type or category of cadet.
-
B.
hasCadetRank
Indicates that an entity holds or is assigned a cadet-level rank within a hierarchical or military-style ranking system.
-
C.
hasCadetProgram
Indicates that an organization or entity offers or operates a cadet program for training or development.
-
D.
hasCadetBranch
chosen
Indicates that one lineage, family, or house is a junior or offshoot branch derived from another main or senior line.
-
E.
hasCadetRankStructure
Indicates that an entity possesses or defines an organizational hierarchy of cadet ranks.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7dfcb508190aec8cd667e27a8ea |
completed | April 15, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:58 a.m.