Triple
T6322607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liam Wright |
E141778
|
entity |
| Predicate | hasPositionSubcategory |
P15481
|
FINISHED |
| Object | back-row forward |
—
|
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: back-row forward | Statement: [Liam Wright, hasPositionSubcategory, back-row forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionSubcategory Context triple: [Liam Wright, hasPositionSubcategory, back-row forward]
-
A.
hasTypeOfSubdivision
Indicates that one administrative or territorial unit is classified as a specific kind or category of subdivision.
-
B.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
C.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
D.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
E.
hasCategoryLevel
Indicates that something is associated with a specific hierarchical category or tier within a classification system.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e38f1c81909c7e90b520602bae |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.