Triple
T32723954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granta |
E836748
|
entity |
| Predicate | relaunched |
P41560
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [Granta, relaunched, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relaunched Context triple: [Granta, relaunched, 1979]
-
A.
relaunch
chosen
Indicates restarting or bringing back into operation something that was previously launched, often with changes or improvements.
-
B.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
C.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
D.
relaunchOrbit
Indicates that an entity is placed back into orbit after having previously left or ceased its orbital path.
-
E.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8b5ab308190b2f5ea97d0614c72 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.