Triple
T1122341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John F. Kennedy Eternal Flame |
E24638
|
entity |
| Predicate | yearOfModernization |
P17897
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [John F. Kennedy Eternal Flame, yearOfModernization, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfModernization Context triple: [John F. Kennedy Eternal Flame, yearOfModernization, 2013]
-
A.
modernizedBy
Indicates that an entity has been updated, improved, or brought up to modern standards through the actions or influence of another entity.
-
B.
renovatedBy
Indicates that an entity has been improved, restored, or updated through renovation work performed by another entity.
-
C.
modernizationPeriod
chosen
Indicates the time span during which an entity undergoes or is subject to modernization efforts or processes.
-
D.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
E.
modernization
Indicates a process by which something is updated, reformed, or transformed to align with contemporary standards, technologies, or practices.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4749ac8190b0fbddac2e9b2586 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.