Triple
T29136184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destiny series |
E738516
|
entity |
| Predicate | hasOnlineRequirement |
P176007
|
FINISHED |
| Object | internet connection |
—
|
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: internet connection | Statement: [Destiny series, hasOnlineRequirement, internet connection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineRequirement Context triple: [Destiny series, hasOnlineRequirement, internet connection]
-
A.
hasOnlineProvision
Indicates that an entity offers or supports a service, feature, or function through an online or internet-based channel.
-
B.
isAvailableOnline
Indicates that something can be accessed or obtained via the internet.
-
C.
hasOnlineForm
Indicates that an entity provides or is associated with a form that can be accessed and completed online.
-
D.
isOnlineOnly
Indicates that the related entity exists, operates, or is accessible exclusively via online or digital channels, with no physical or offline presence.
-
E.
hasOnlineReception
Indicates that an entity provides or supports a reception, front-desk, or greeting function through online or digital channels rather than solely in person.
- F. None of above. chosen
Provenance (4 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 28, 2026, 11:34 a.m.