Triple
T15721396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyndon Ferns |
E381101
|
entity |
| Predicate | teamEventSpecialty |
P119916
|
FINISHED |
| Object | relay swimming events |
—
|
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: relay swimming events | Statement: [Lyndon Ferns, teamEventSpecialty, relay swimming events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamEventSpecialty Context triple: [Lyndon Ferns, teamEventSpecialty, relay swimming events]
-
A.
teamSpecialty
Indicates the particular area of expertise or focus that characterizes a team’s skills or activities.
-
B.
eventSpecialty
Indicates the specific field, theme, or area of focus that an event is primarily concerned with.
-
C.
teamDuringEvent
Indicates that a particular team is associated with, participates in, or is active during a specified event.
-
D.
specialtyEvent
Indicates that an event is designated as a special or distinctive occurrence, often differing from regular or routine events in nature or purpose.
-
E.
associatedWithTeamSport
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb0b51081908e652ec4992296fa |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:45 a.m.