Triple
T27206918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese women’s distance running squad |
E683889
|
entity |
| Predicate | specializedEvent |
P168942
|
FINISHED |
| Object | 3000 metres |
—
|
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: 3000 metres | Statement: [Chinese women’s distance running squad, specializedEvent, 3000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specializedEvent Context triple: [Chinese women’s distance running squad, specializedEvent, 3000 metres]
-
A.
specialtyEvent
Indicates that an event is designated as a special or distinctive occurrence, often differing from regular or routine events in nature or purpose.
-
B.
specialEventServiceTo
Indicates that a service is specifically provided or designated for a particular special event.
-
C.
eventSpecialty
Indicates the specific field, theme, or area of focus that an event is primarily concerned with.
-
D.
selectedEvent
Indicates that a particular event has been chosen or designated from a set of possible events.
-
E.
alternativeEvent
Indicates that one event serves as an alternative or substitute option to another event within the same context.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 9:38 a.m.