Triple
T11936856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | For SAAM |
E284066
|
entity |
| Predicate | hasMediumSupport |
P182
|
FINISHED |
| Object | electronic signage |
—
|
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: electronic signage | Statement: [For SAAM, hasMediumSupport, electronic signage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediumSupport Context triple: [For SAAM, hasMediumSupport, electronic signage]
-
A.
hasSupported
Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
-
B.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
hasMediumCharacter
Indicates that one entity possesses or is associated with a character whose size, intensity, or degree is classified as medium.
-
D.
requiresMedium
Indicates that an action or process depends on or must be carried out within a specific medium or environment to occur or be valid.
-
E.
hasPageMedium
Indicates that a page or document is associated with a particular physical or digital medium through which it is presented or stored.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903094218819092e11b273d87de65 |
completed | April 10, 2026, 2:02 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.