Triple
T20337916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of Lusignan |
E495662
|
entity |
| Predicate | fieldSymbolism |
P139747
|
FINISHED |
| Object | noble lineage |
—
|
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: noble lineage | Statement: [Arms of Lusignan, fieldSymbolism, noble lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldSymbolism Context triple: [Arms of Lusignan, fieldSymbolism, noble lineage]
-
A.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
-
B.
symbolismFocus
Indicates that the primary emphasis of a work, element, or representation is on its symbolic meaning rather than its literal or functional aspects.
-
C.
symbolismIn
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
-
D.
treeSymbolism
Indicates the use of a tree as a symbolic representation of an idea, quality, or relationship between entities.
-
E.
incorporatesSymbolismFrom
Indicates that one entity includes or integrates symbolic elements, motifs, or meanings derived from another entity.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678332bd08190a83880fb6aa32e08 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:23 a.m.