Triple
T6847841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma City National Memorial |
E157940
|
entity |
| Predicate | designSelected |
P72573
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Oklahoma City National Memorial, designSelected, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designSelected Context triple: [Oklahoma City National Memorial, designSelected, 1997]
-
A.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
B.
designModel
Indicates that one entity creates, specifies, or defines the structure or behavior of another entity as a model or blueprint.
-
C.
designVariant
Indicates that one entity is an alternative design or version derived from or related to another entity’s design.
-
D.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
E.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d7ce3e7481908e0472b8faafa473 |
completed | March 27, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:20 p.m.