Triple
T29870707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider-Verse suit |
E758586
|
entity |
| Predicate | supportsPhotoMode |
P57608
|
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: [Spider-Verse suit, supportsPhotoMode, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPhotoMode Context triple: [Spider-Verse suit, supportsPhotoMode, yes]
-
A.
hasPhotoFeature
chosen
Indicates that an entity possesses a characteristic, capability, or option specifically related to photos or photography.
-
B.
hasPhotogenicFeature
Indicates that an entity possesses a visual characteristic or attribute that is especially attractive or appealing when photographed.
-
C.
supportsCameraControl
Indicates that one entity provides functionality for another entity to remotely manage or adjust camera settings or operations.
-
D.
hasAIPhotoFeatures
Indicates that an entity provides or supports photo-related features powered by artificial intelligence.
-
E.
hasDedicatedCameraButton
Indicates that an object or device includes a specific physical button intended solely for activating or controlling the camera function.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:53 p.m.