Triple
T19218219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corteo |
E480540
|
entity |
| Predicate | hasRelaunchRunStart |
P135024
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Corteo, hasRelaunchRunStart, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelaunchRunStart Context triple: [Corteo, hasRelaunchRunStart, 2018]
-
A.
hasLaunchedFor
Indicates that an entity (such as a product, feature, or service) has been officially released or made available specifically for another entity (such as a user, group, market, or platform).
-
B.
hasLaunch
Indicates that an entity initiates or carries out the launch of another entity (such as a product, mission, or event).
-
C.
hasLaunchHistoryEvent
Indicates that there exists a recorded event in the launch history associated with the given entity.
-
D.
hasRun
Indicates that an entity has performed or completed a running activity or event at least once in the past.
-
E.
hasLaunchContext
Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3c552c8190b22844e5b7adfc50 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:23 p.m.