Triple
T29247976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3DO |
E741487
|
entity |
| Predicate | subsequentLaunchRegion |
P167407
|
FINISHED |
| Object | Japan |
—
|
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: Japan | Statement: [3DO, subsequentLaunchRegion, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentLaunchRegion Context triple: [3DO, subsequentLaunchRegion, Japan]
-
A.
secondLaunchOutcome
Indicates the result or status of the entity’s second launch attempt or event.
-
B.
continuedInRegion
Indicates that an event, process, or state persisted or carried on within a specified geographic or spatial region.
-
C.
successorInRegion
Indicates that one entity directly follows or replaces another within a specified region or jurisdiction.
-
D.
subsequentLandRuns
Indicates that one land run event occurred after another in temporal sequence.
-
E.
nextGenerationLaunch
Indicates the initiation or deployment of a subsequent, more advanced version of a product, system, or technology.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 12:33 p.m.