Triple
T26989487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | With Love |
E679826
|
entity |
| Predicate | platformDebutTerritory |
P163863
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [With Love, platformDebutTerritory, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformDebutTerritory Context triple: [With Love, platformDebutTerritory, worldwide]
-
A.
releasePlatformRegion
chosen
Indicates the specific geographic region or market where a release (such as a product, service, or media title) is made available on a given platform.
-
B.
emergedOnPlatform
Indicates that an entity became visible, active, or came into existence on a specified platform.
-
C.
announcedPlatform
Indicates that an entity has publicly revealed or introduced a particular platform (such as a system, service, or technology).
-
D.
launchedInCountry
Indicates that an entity (such as a product, service, or mission) was officially initiated, introduced, or started within a specified country.
-
E.
platformFirstReleased
Indicates the date or time when a platform was initially released or made publicly available.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 6:50 a.m.