Triple
T20513547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 38 Studios |
E503623
|
entity |
| Predicate | statusOfProjectCopernicus |
P70876
|
FINISHED |
| Object | cancelled |
—
|
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: cancelled | Statement: [38 Studios, statusOfProjectCopernicus, cancelled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfProjectCopernicus Context triple: [38 Studios, statusOfProjectCopernicus, cancelled]
-
A.
statusOfOriginalProject
chosen
Indicates the current state or condition of the original project in relation to its lifecycle or progress.
-
B.
observationalStatus
Indicates the current state or condition of an observation, such as whether it has been made, recorded, verified, or remains pending.
-
C.
ESAStatus
Indicates the conservation status of an entity as defined under the U.S. Endangered Species Act (e.g., endangered, threatened, candidate).
-
D.
IAUStatus
Indicates the formal classification or recognition status of an astronomical object or entity as defined by the International Astronomical Union (IAU).
-
E.
universeStatus
Indicates the current overall state or condition of a universe within a given system or context.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f4066908190a94724697fb8cdcb |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.