Triple
T15368867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Targa Tasmania |
E367489
|
entity |
| Predicate | attractsParticipants |
P1347
|
FINISHED |
| Object | professional drivers |
—
|
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: professional drivers | Statement: [Targa Tasmania, attractsParticipants, professional drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attractsParticipants Context triple: [Targa Tasmania, attractsParticipants, professional drivers]
-
A.
attractsParticipantsFrom
Indicates that an event, activity, or organization draws or recruits participants originating from a specified place, group, or source.
-
B.
welcomesParticipantsOf
Indicates that one entity receives or greets the participants associated with another entity in a friendly or accepting manner.
-
C.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
D.
attracts
chosen
Indicates that one entity exerts a force or influence that draws another entity toward it.
-
E.
attractsAudience
Indicates that an entity draws the interest or attention of people who choose to watch, listen to, or engage with it.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e4b88a881909f9575c02aed287d |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca9ab7e88190a9261ef27be665b1 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.