Triple
T17843525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Maitland |
E445593
|
entity |
| Predicate | arms |
P129389
|
FINISHED |
| Object | Or, a lion rampant Gules within a double tressure flory counterflory Azure |
—
|
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: Or, a lion rampant Gules within a double tressure flory counterflory Azure | Statement: [Clan Maitland, arms, Or, a lion rampant Gules within a double tressure flory counterflory Azure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arms Context triple: [Clan Maitland, arms, Or, a lion rampant Gules within a double tressure flory counterflory Azure]
-
A.
hasArms
Indicates that an entity possesses arms as physical appendages.
-
B.
armType
Indicates the specific kind or configuration of an arm associated with an entity.
-
C.
armed
Indicates that an entity is equipped with or carrying a weapon or weapons.
-
D.
armsControl
Indicates a relationship where parties engage in limiting, regulating, or reducing weapons and military capabilities, often through agreements or treaties.
-
E.
supportingArms
Indicates that one entity provides military or tactical support, such as firepower or cover, to assist another entity’s operations.
- F. None of above. chosen
Provenance (4 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ff8730881908cc8e1b572fa0af8 |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3f022ec448190a9bf191be1c5f570 |
completed | April 18, 2026, 8:57 p.m. |
Created at: April 10, 2026, 10:16 a.m.