Triple
T28828605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptune |
E727980
|
entity |
| Predicate | plannedEditionType |
P82306
|
FINISHED |
| Object | home 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: home edition | Statement: [Neptune, plannedEditionType, home edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedEditionType Context triple: [Neptune, plannedEditionType, home edition]
-
A.
hasEditionType
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
-
B.
majorEditionsPlanned
chosen
Indicates that significant future versions or releases of an entity (such as a work, product, or publication) are scheduled or intended to be produced.
-
C.
publisherPlanned
Indicates that a publisher has scheduled or intends to release or distribute a particular work or item.
-
D.
editionPattern
Indicates a recurring structure or template that characterizes how different editions or versions of something are organized or produced.
-
E.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
- 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_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 6:37 a.m.