Triple
T11631959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Border Collie |
E276418
|
entity |
| Predicate | trainabilityLevel |
P4144
|
FINISHED |
| Object | exceptionally high |
—
|
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: exceptionally high | Statement: [Border Collie, trainabilityLevel, exceptionally high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainabilityLevel Context triple: [Border Collie, trainabilityLevel, exceptionally high]
-
A.
trainingLevel
chosen
Indicates the degree or stage of training or skill development that an entity has attained.
-
B.
providesTrainingFor
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
-
C.
trainingCharacteristic
Indicates that an entity has a specific property, feature, or quality related to training (such as method, intensity, or style).
-
D.
trainingUnder
Indicates that one entity is receiving instruction, guidance, or mentorship from another, typically in a subordinate or apprentice-like capacity.
-
E.
trainingGround
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25aa9188190ab13d79139f37e7e |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.