Triple
T20335189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Professionals |
E492588
|
entity |
| Predicate | hasLiveActivity |
P19746
|
FINISHED |
| Object | UK tours |
—
|
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: UK tours | Statement: [The Professionals, hasLiveActivity, UK tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveActivity Context triple: [The Professionals, hasLiveActivity, UK tours]
-
A.
hasOnlineActivity
Indicates that an entity engages in or possesses some form of activity or presence on the internet or digital platforms.
-
B.
hasRecentActivity
Indicates that the subject has performed an action or been involved in an event within a defined recent time period.
-
C.
hasActivityIn
chosen
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
D.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
E.
hasInteractiveActivity
Indicates that an entity includes or is associated with an activity that requires active user participation or engagement.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677ea8a088190b2b37accd6b24277 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:23 a.m.