Triple
T2950927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dambana ng Kagitingan |
E79816
|
entity |
| Predicate | visitorPurpose |
P24037
|
FINISHED |
| Object | war remembrance |
—
|
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: war remembrance | Statement: [Dambana ng Kagitingan, visitorPurpose, war remembrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorPurpose Context triple: [Dambana ng Kagitingan, visitorPurpose, war remembrance]
-
A.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
-
B.
visitorUse
Indicates that an entity is being used, accessed, or engaged with by a visitor or temporary user.
-
C.
visitorProfile
Indicates a relationship where a profile encapsulates information or attributes associated with a particular visitor.
-
D.
typicalJourneyPurpose
chosen
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
-
E.
visitorRequirement
Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98fbb7d4819081c241f3ff9165e5 |
completed | March 8, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.