Triple
T11656903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joost |
E277031
|
entity |
| Predicate | laterPlatformChange |
P30268
|
FINISHED |
| Object | web-based video service |
—
|
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: web-based video service | Statement: [Joost, laterPlatformChange, web-based video service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPlatformChange Context triple: [Joost, laterPlatformChange, web-based video service]
-
A.
laterPlatform
chosen
Indicates that one entity occurs, appears, or is positioned on a platform that comes after another platform in time or sequence.
-
B.
replacedPlatform
Indicates that one platform has been superseded or taken over by another platform.
-
C.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
D.
launchPlatformFor
Indicates a relationship where one entity serves as the platform or site from which another entity is launched.
-
E.
laterFeature
Indicates that one feature, event, or element occurs or is introduced after another in time.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d0331481909682b2e504e4c9a0 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.