Triple
T20657176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Division Memorial |
E507656
|
entity |
| Predicate | addedSculpturalGroup |
P62553
|
FINISHED |
| Object | World War II battle honors |
—
|
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: World War II battle honors | Statement: [Second Division Memorial, addedSculpturalGroup, World War II battle honors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedSculpturalGroup Context triple: [Second Division Memorial, addedSculpturalGroup, World War II battle honors]
-
A.
usesSculptureFor
Indicates that one entity employs or utilizes a sculpture for a particular purpose, function, or activity.
-
B.
addedStructure
chosen
Indicates that one entity has introduced or incorporated an additional structural element into another entity or system.
-
C.
assistantSculptor
Indicates a relationship where one entity serves as an assistant to another entity in the role or activity of sculpting.
-
D.
hasSculptor
Indicates that one entity serves as the sculptor (creator of a sculpture) of another entity.
-
E.
laterSculptor
Indicates that one sculptor chronologically follows another, working in a later period or phase.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2ee049081909904efe2dc683cd5 |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.