Triple
T33540071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Swimming Trials |
E859045
|
entity |
| Predicate | timingRelativeToWorlds |
P176871
|
FINISHED |
| Object | held in World Championships year |
—
|
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: held in World Championships year | Statement: [Australian Swimming Trials, timingRelativeToWorlds, held in World Championships year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timingRelativeToWorlds Context triple: [Australian Swimming Trials, timingRelativeToWorlds, held in World Championships year]
-
A.
positionInWorlds
Indicates that an entity occupies specific spatial coordinates or locations within one or more distinct worlds or environments.
-
B.
relationshipToWorld
Indicates how an entity is connected or related to the broader world or external environment.
-
C.
timingOfPoints
Indicates the temporal relationship or sequence in which the points or events occur.
-
D.
timeCoordinate
Indicates a relationship where a specific time value is used to locate or reference an event, state, or object along a temporal axis or timeline.
-
E.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:39 a.m.