Triple
T18739991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormont, Belfast |
E458262
|
entity |
| Predicate | hostsFormat |
P52057
|
FINISHED |
| Object | One Day International |
—
|
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: One Day International | Statement: [Stormont, Belfast, hostsFormat, One Day International]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsFormat Context triple: [Stormont, Belfast, hostsFormat, One Day International]
-
A.
hostFullName
Indicates that one entity is the complete personal name (including given and family names, and possibly middle names or titles) of the host associated with another entity.
-
B.
hostsPartOf
Indicates that one entity serves as the hosting environment or container for a specific part or component of another entity.
-
C.
hostType
chosen
Indicates the category or kind of host associated with or responsible for the related entity or activity.
-
D.
hostsFictional
Indicates that one entity serves as the setting, platform, or environment in which a fictional character, event, or work is situated or presented.
-
E.
host
Indicates that one entity provides space, resources, or services to accommodate, receive, or entertain another entity.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5768d6a208190817abe904fab433b |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.