Triple
T7642580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shopDisney |
E173041
|
entity |
| Predicate | hasDigitalPlatformType |
P57
|
FINISHED |
| Object | website |
—
|
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: website | Statement: [shopDisney, hasDigitalPlatformType, website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalPlatformType Context triple: [shopDisney, hasDigitalPlatformType, website]
-
A.
hasDigitalSystem
Indicates that an entity possesses, uses, or is equipped with a digital system (such as software, hardware, or an integrated digital platform).
-
B.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
-
C.
hasOnlinePlatform
chosen
Indicates that an entity operates, maintains, or is associated with a presence or service on an online platform.
-
D.
hasPrimaryPlatform
Indicates that one entity is designated as the main or principal platform associated with another entity.
-
E.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faef96908190a7724b204f9d8c9e |
completed | March 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:58 p.m.