Triple
T33128624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Canada Hockey League |
E847790
|
entity |
| Predicate | hasScoutingPresenceFrom |
P191819
|
FINISHED |
| Object | major junior teams |
—
|
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: major junior teams | Statement: [Central Canada Hockey League, hasScoutingPresenceFrom, major junior teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoutingPresenceFrom Context triple: [Central Canada Hockey League, hasScoutingPresenceFrom, major junior teams]
-
A.
scoutedFor
Indicates that one entity has been evaluated or searched out as a potential candidate, resource, or opportunity on behalf of another entity.
-
B.
hasNotableTribeAtEncounter
Indicates that, at the time of the encounter, the entity was associated with or identified as belonging to a notable tribe.
-
C.
enemyPresence
Indicates the presence of hostile or adversarial entities in relation to a specified entity or location.
-
D.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
E.
hasSight
Indicates that one entity possesses the ability or capacity to see or visually perceive.
- 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: May 1, 2026, 1:27 a.m.