Triple
T11657741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series 90 |
E277051
|
entity |
| Predicate | supportsPortraitMode |
P56041
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Series 90, supportsPortraitMode, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPortraitMode Context triple: [Series 90, supportsPortraitMode, true]
-
A.
hasPortrait
Indicates that one entity possesses, displays, or is associated with a portrait depicting another entity.
-
B.
supportsConnectorOrientation
Indicates that one entity is capable of accommodating or functioning correctly with a specified orientation of a connector relative to another entity.
-
C.
performanceOrientation
Indicates a relationship where an entity is characterized by a focus on achieving high performance, results, or measurable outcomes in its activities or behavior.
-
D.
supportsVerticalVideo
chosen
Indicates that one entity provides compatibility with or proper handling of vertical (portrait-oriented) video content for another entity.
-
E.
supportsHandheldMode
Indicates that an entity is capable of operating or being used in a handheld mode.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d0331481909682b2e504e4c9a0 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.