Triple
T8470571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quick Look |
E200269
|
entity |
| Predicate | supportsMetadataDisplay |
P41649
|
FINISHED |
| Object | file information overlay |
—
|
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: file information overlay | Statement: [Quick Look, supportsMetadataDisplay, file information overlay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMetadataDisplay Context triple: [Quick Look, supportsMetadataDisplay, file information overlay]
-
A.
supportsMultipleDataAndDisplayProtocols
Indicates that an entity is capable of handling more than one type of data protocol and more than one type of display protocol.
-
B.
supportsSecuritySchemesDisplay
Indicates that an entity enables or allows the presentation or visualization of associated security schemes.
-
C.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
D.
displaysFeature
chosen
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
-
E.
supportsMultipleServersDisplay
Indicates that an entity can correctly handle and present information for more than one server simultaneously.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.