Triple
T32713189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iten |
E836451
|
entity |
| Predicate | hasTrainingCamp |
P46335
|
FINISHED |
| Object | High Altitude Training Centre |
—
|
NE NERFINISHED |
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: High Altitude Training Centre | Statement: [Iten, hasTrainingCamp, High Altitude Training Centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingCamp Context triple: [Iten, hasTrainingCamp, High Altitude Training Centre]
-
A.
trainingCamps
chosen
Indicates that one entity organizes, hosts, or is associated with training camps for another entity or group.
-
B.
hasSportsSpringTraining
Indicates that an entity conducts, hosts, or is associated with spring training activities for a sports team or sports organization.
-
C.
hasPracticeWeek
Indicates that an entity is associated with a specific week designated for practice activities or sessions.
-
D.
hasBootCamp
Indicates that an entity offers, hosts, or is associated with a boot camp program or event.
-
E.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: May 1, 2026, 1:11 a.m.