Triple
T11071104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orders, decorations, and medals of the Philippines |
E261746
|
entity |
| Predicate | hasInsigniaTypes |
P1617
|
FINISHED |
| Object | neck badge |
—
|
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: neck badge | Statement: [Orders, decorations, and medals of the Philippines, hasInsigniaTypes, neck badge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInsigniaTypes Context triple: [Orders, decorations, and medals of the Philippines, hasInsigniaTypes, neck badge]
-
A.
hasTypeOfInsignia
chosen
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
B.
hasInsigniaComponent
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
-
C.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
D.
insigniaName
Indicates the specific name or designation assigned to an insignia associated with an entity.
-
E.
hasSignageType
Indicates the specific category or kind of signage associated with an object, location, or 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79922e48c81909adb161e66f47474 |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.