Triple
T4893017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Response Framework |
E109607
|
entity |
| Predicate | updatedEdition |
P60447
|
FINISHED |
| Object | second edition |
—
|
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: second edition | Statement: [National Response Framework, updatedEdition, second edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedEdition Context triple: [National Response Framework, updatedEdition, second edition]
-
A.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
B.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
C.
updatesVersionOf
Indicates that one entity is a newer or modified version that replaces or supersedes another entity.
-
D.
nextEdition
Indicates that one entity is the immediate subsequent edition or version that follows another in a sequence.
-
E.
lastEdition
Indicates that one entity is the most recent or final edition/version within a series or sequence of editions.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffabccc81909115ece1b04e2061 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2e7b5c8190b8bf9d616dfa24f0 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:28 p.m.