Triple
T21423326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planetfall |
E528490
|
entity |
| Predicate | supportsTextOnlyDisplay |
P76291
|
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, supportsTextOnlyDisplay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTextOnlyDisplay Context triple: [Planetfall, supportsTextOnlyDisplay, yes]
-
A.
supportsTextFormat
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified text format.
-
B.
supportsDisplayTechnology
chosen
Indicates that one entity is compatible with, or capable of operating using, a specified display technology.
-
C.
supportsDisplayStandard
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
-
D.
supportsAnalogOnly
Indicates that the subject provides or is compatible only with analog functionality, and does not support any digital capabilities.
-
E.
supportsMonochromeMonitor
Indicates that one entity is capable of operating with, driving, or is compatible with a monochrome (single-color) monitor.
- 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.