Triple
T28828594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptune |
E727980
|
entity |
| Predicate | plannedSuccessorOf |
P98729
|
FINISHED |
| Object | Windows 98 Second Edition |
—
|
NE NERFINISHED |
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: Windows 98 Second Edition | Statement: [Neptune, plannedSuccessorOf, Windows 98 Second Edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedSuccessorOf Context triple: [Neptune, plannedSuccessorOf, Windows 98 Second Edition]
-
A.
intendedSuccessorTo
chosen
Indicates that one entity is meant or designated to follow, replace, or take over the role or position of another entity in the future.
-
B.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
C.
successorControlledBy
Indicates that the successor entity is governed, directed, or significantly influenced by another controlling entity.
-
D.
successorRelationship
Indicates a relationship where one entity directly follows or replaces another in a sequence, order, or role.
-
E.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 6:36 a.m.