Triple
T18572964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of Singapore |
E453914
|
entity |
| Predicate | tigerSymbolism |
P41568
|
FINISHED |
| Object | historical ties with Malaysia |
—
|
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: historical ties with Malaysia | Statement: [Coat of arms of Singapore, tigerSymbolism, historical ties with Malaysia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tigerSymbolism Context triple: [Coat of arms of Singapore, tigerSymbolism, historical ties with Malaysia]
-
A.
animalSymbol
chosen
Indicates that one entity serves as a symbolic representation or emblem of the other in the form of an animal.
-
B.
treeSymbolism
Indicates the use of a tree as a symbolic representation of an idea, quality, or relationship between entities.
-
C.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
-
D.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
E.
symbolismIn
Indicates that one entity functions as a symbol or representation within the context, meaning, or interpretive framework of another entity.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b032488819098de683bb5c42c4b |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.