Triple
T24588637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 Summer Universiade |
E608465
|
entity |
| Predicate | isUniversiade |
P156465
|
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: [2005 Summer Universiade, isUniversiade, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUniversiade Context triple: [2005 Summer Universiade, isUniversiade, true]
-
A.
universitySport
Indicates a relationship where a particular sport is officially associated with, offered, or organized by a university.
-
B.
isIntercollegiate
Indicates that an activity, competition, or relationship occurs between different colleges or universities rather than within a single institution.
-
C.
isUrbanUniversity
Indicates that a university is located in, or primarily associated with, an urban (city) environment.
-
D.
representedUniversity
Indicates that one entity has formally acted on behalf of, or served as a representative of, a particular university.
-
E.
participatingUniversity
Indicates that a university is taking part in or contributing to a specific event, project, program, or collaboration.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9898f708190b521317207c79f64 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:29 a.m.