Triple
T24928465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GIF |
E618925
|
entity |
| Predicate | updatedAs |
P4421
|
FINISHED |
| Object | 89a specification |
—
|
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: 89a specification | Statement: [GIF, updatedAs, 89a specification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatedAs Context triple: [GIF, updatedAs, 89a specification]
-
A.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
B.
updatedFrom
Indicates that one entity is a newer or modified version derived from another earlier entity.
-
C.
updated
chosen
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
D.
alsoUpdatedBy
Indicates that an entity, in addition to others, has been modified or changed by the specified agent or source.
-
E.
updatesFrom
Indicates that one entity is revised, modified, or brought to a newer state based on information, changes, or content originating from 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:29 a.m.