Triple
T1162933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National World War I Memorial |
E24533
|
entity |
| Predicate | designCompetitionHeld |
P22324
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [National World War I Memorial, designCompetitionHeld, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designCompetitionHeld Context triple: [National World War I Memorial, designCompetitionHeld, 2015]
-
A.
architecturalCompetition
Indicates that there is a formal design contest held to select among competing architectural proposals or architects for a specific project or purpose.
-
B.
designCompetitionWonBy
Indicates that a particular design competition was won by a specified participant or entity.
-
C.
designCompetitionYear
chosen
Indicates the year in which a particular design competition took place or is associated with.
-
D.
skillsCompetitionEvent
Indicates that a competitive event is held to assess and compare participants’ skills or abilities.
-
E.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcb2bb84819088bd94e91c10fb0c |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.