Triple
T36769281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine National Heroes Day |
E908429
|
entity |
| Predicate | sectorHonored |
P186279
|
FINISHED |
| Object | military heroes |
—
|
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: military heroes | Statement: [Philippine National Heroes Day, sectorHonored, military heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorHonored Context triple: [Philippine National Heroes Day, sectorHonored, military heroes]
-
A.
sectorProtected
Indicates that a particular sector or area is safeguarded from harm, access, or exploitation by some form of protection or regulation.
-
B.
sectorIncludes
Indicates that a broader sector encompasses or contains a specified sub-sector, area, or component within its scope.
-
C.
sectorGoverned
Indicates that a particular sector or domain is under the authority, control, or regulatory oversight of a specified governing entity.
-
D.
sectorRecognized
Indicates that an entity has been formally acknowledged or classified within a particular sector or industry.
-
E.
sectorRepresented
Indicates that an entity serves as a representative or proxy for a particular sector (such as an industry, domain, or market segment).
- F. None of above. chosen
Provenance (4 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:12 p.m.