Triple
T22628284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Dinh |
E558480
|
entity |
| Predicate | hasMemorialElements |
P148979
|
FINISHED |
| Object | displays honoring Viet Cong fighters |
—
|
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: displays honoring Viet Cong fighters | Statement: [Ben Dinh, hasMemorialElements, displays honoring Viet Cong fighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemorialElements Context triple: [Ben Dinh, hasMemorialElements, displays honoring Viet Cong fighters]
-
A.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
B.
hasMemorialContext
Indicates that something is related to, associated with, or situated within the context of a memorial or commemorative setting.
-
C.
hasMemorialWall
Indicates that a place or entity includes or is associated with a wall dedicated to commemorating people, events, or memories.
-
D.
hasAdjacentMemorial
Indicates that one memorial is located directly next to or in close proximity to another memorial.
-
E.
hasMemorialRoom
Indicates that an entity possesses or contains a dedicated room serving as a memorial to a person, group, or event.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3ed1d48190a093013d829901b9 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:02 p.m.