Triple
T18941602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of San Marino |
E463394
|
entity |
| Predicate | oakSymbolism |
P70570
|
FINISHED |
| Object | strength |
—
|
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: strength | Statement: [Coat of arms of San Marino, oakSymbolism, strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oakSymbolism Context triple: [Coat of arms of San Marino, oakSymbolism, strength]
-
A.
oakTreeSymbolizes
chosen
Indicates that an oak tree is used as a symbol representing a particular idea, quality, or concept.
-
B.
treeSymbolism
Indicates the use of a tree as a symbolic representation of an idea, quality, or relationship between entities.
-
C.
oakAffinity
Indicates a special connection, preference, or strong association between an entity and oak (such as oak trees, wood, or oak-related environments).
-
D.
oakRegimen
Indicates a prescribed or customary course of actions, treatments, or behaviors associated with the entity referred to as "oak."
-
E.
oakTypeUsed
Indicates that a particular type of oak is used in relation to another entity, such as in construction, manufacturing, or production.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3eba60081909c9027d1988f88ad |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.