Triple
T21423318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planetfall |
E528490
|
entity |
| Predicate | hasCopyProtection |
P17307
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Planetfall, hasCopyProtection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCopyProtection Context triple: [Planetfall, hasCopyProtection, yes]
-
A.
usesDRM
chosen
Indicates that one entity applies digital rights management (DRM) controls or technologies to another entity (such as content, software, or media).
-
B.
hasCopyleft
Indicates that a work, license, or component is subject to copyleft terms requiring derivative or combined works to be distributed under the same or compatible license conditions.
-
C.
hasLandscapeProtection
Indicates that an area or object is subject to legal or formal measures aimed at preserving its landscape or scenic character.
-
D.
supportsReplayProtection
Indicates that the action or system includes mechanisms to prevent replaying previously valid messages or transactions as if they were new.
-
E.
hasCopy
Indicates that one entity possesses, contains, or maintains a duplicate or instance 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee8139ce848190b812d6d07f1bdef8 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:48 p.m.