Triple
T31910099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matt Burke |
E814655
|
entity |
| Predicate | hasMainPosition |
P14496
|
FINISHED |
| Object | fullback |
—
|
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: fullback | Statement: [Matt Burke, hasMainPosition, fullback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPosition Context triple: [Matt Burke, hasMainPosition, fullback]
-
A.
hasMainRole
chosen
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
B.
hasDominantPosition
Indicates that one entity holds a superior, controlling, or more influential position over another within a given context or structure.
-
C.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
D.
hasMainStandOn
Indicates that one entity serves as the primary physical support structure or main stand for another entity.
-
E.
hasMainRepresentative
Indicates that one entity serves as the primary or official representative of 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: May 1, 2026, 12:01 a.m.