Triple
T19995813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netherlands American Cemetery and Memorial |
E494188
|
entity |
| Predicate | formalDedication |
P138267
|
FINISHED |
| Object | 1960 |
—
|
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: 1960 | Statement: [Netherlands American Cemetery and Memorial, formalDedication, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalDedication Context triple: [Netherlands American Cemetery and Memorial, formalDedication, 1960]
-
A.
dedicatee
Indicates the person or entity to whom a work, such as a book, artwork, or performance, is formally dedicated.
-
B.
dedicationMessage
Indicates that one entity expresses a formal dedication or tribute message directed toward another entity or purpose.
-
C.
dedicationBy
Indicates that one entity formally dedicates, commits, or devotes another entity (such as a work, resource, or effort) to a particular person, purpose, or cause.
-
D.
dedicationType
Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
-
E.
dedicateeTitle
Indicates the formal title or honorific held by the person to whom something (such as a work or object) is dedicated.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe3fb288190a935c334e8a5d54e |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:32 p.m.