Triple
T28670680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITF Seniors Tour |
E725708
|
entity |
| Predicate | hasTeamEvents |
P160643
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ITF Seniors Tour, hasTeamEvents, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamEvents Context triple: [ITF Seniors Tour, hasTeamEvents, true]
-
A.
isTeamEventIncluded
chosen
Indicates whether a particular team event is counted or considered as part of a specified set, schedule, or collection of events.
-
B.
hasOfficialEvents
Indicates that an entity organizes, hosts, or is associated with formally recognized or sanctioned events.
-
C.
hasSportingEvent
Indicates that a sporting event is associated with, held at, or organized by a given entity.
-
D.
hasPublicEventsIn
Indicates that an entity organizes or holds public events within a specified location or context.
-
E.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 28, 2026, 5:03 a.m.