Triple
T14824468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queensland Cup |
E348534
|
entity |
| Predicate | hasTalentLevel |
P2393
|
FINISHED |
| Object | sub-elite |
—
|
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: sub-elite | Statement: [Queensland Cup, hasTalentLevel, sub-elite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTalentLevel Context triple: [Queensland Cup, hasTalentLevel, sub-elite]
-
A.
grantedTalentBy
Indicates that a talent, skill, or special ability is conferred upon an entity by another entity as the granting source.
-
B.
hasCompetence
Indicates that an entity possesses the ability, skill, or qualification to perform a specific task or function effectively.
-
C.
hasLevel
chosen
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
D.
hasEponymousSkill
Indicates that an entity possesses a skill that is named after a particular person or entity.
-
E.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe7a8dc8190bcb5ecfa1cbf1601 |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:51 a.m.