Triple
T27330911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vickers Varsity |
E689795
|
entity |
| Predicate | primaryConfiguration |
P55012
|
FINISHED |
| Object | trainer |
—
|
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: trainer | Statement: [Vickers Varsity, primaryConfiguration, trainer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryConfiguration Context triple: [Vickers Varsity, primaryConfiguration, trainer]
-
A.
primarySetting
Indicates that one entity serves as the main or central location, context, or environment in which the other entity’s events or activities primarily take place.
-
B.
primarySettingOf
Indicates that a location or context serves as the main or principal setting in which an entity (such as a story, event, or activity) takes place.
-
C.
primaryFor
chosen
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
D.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
-
E.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 27, 2026, 11:38 a.m.