Triple
T4858777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of Midlothian F.C. |
E108602
|
entity |
| Predicate | hasTrainingGround |
P2424
|
FINISHED |
| Object | Oriam (used as training base) |
—
|
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: Oriam (used as training base) | Statement: [Heart of Midlothian F.C., hasTrainingGround, Oriam (used as training base)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingGround Context triple: [Heart of Midlothian F.C., hasTrainingGround, Oriam (used as training base)]
-
A.
trainingGroundFor
Indicates that one entity serves as a place or context where another entity is trained, prepared, or developed.
-
B.
trainingGround
chosen
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
-
C.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
D.
hasTrainingRole
Indicates that an entity holds or is assigned a specific role within a training or instructional context.
-
E.
hasTrained
Indicates that one entity has provided training or instruction to another entity.
- 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_69bd440b965081908b0557721cae6338 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d5b2f008190a5fd11d3aec165fb |
completed | March 20, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.