Triple
T35536673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine Veterans Week |
E1026949
|
entity |
| Predicate | mainHonorees |
P145682
|
FINISHED |
| Object | Filipino war veterans |
—
|
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: Filipino war veterans | Statement: [Philippine Veterans Week, mainHonorees, Filipino war veterans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainHonorees Context triple: [Philippine Veterans Week, mainHonorees, Filipino war veterans]
-
A.
hasHonorees
chosen
Indicates that one entity is recognized or celebrated by listing another entity or entities as its honorees.
-
B.
honoreeHallOfFame
Indicates that an entity is recognized as an inductee or honoree in a particular Hall of Fame.
-
C.
honoredPerson
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
-
D.
typicalHonoree
Indicates that an entity is the usual or characteristic recipient of an honor, award, or recognition associated with another entity.
-
E.
honoreeField
Indicates that one entity is recognized or designated as the honoree associated with another entity, such as an award, event, or dedication.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.