Triple
T15804595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of Arms of Singapore |
E383177
|
entity |
| Predicate | featuresShieldSymbol |
P108401
|
FINISHED |
| Object | white crescent moon |
—
|
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: white crescent moon | Statement: [Coat of Arms of Singapore, featuresShieldSymbol, white crescent moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresShieldSymbol Context triple: [Coat of Arms of Singapore, featuresShieldSymbol, white crescent moon]
-
A.
featuresShield
Indicates that an entity includes or is equipped with a shield as one of its characteristics or components.
-
B.
featuresOnShield
chosen
Indicates that something is depicted or displayed as a design element on a shield.
-
C.
shieldPresent
Indicates that a protective shield is currently active or available in the given context.
-
D.
shieldType
Indicates the specific kind or category of shield associated with an entity or interaction.
-
E.
securityFeature
Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b525b1c08190acffab06d89dbdbe |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.