Triple
T14543375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007 NRL season |
E341225
|
entity |
| Predicate | DallyMPosition |
P114865
|
FINISHED |
| Object | halfback |
—
|
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: halfback | Statement: [2007 NRL season, DallyMPosition, halfback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DallyMPosition Context triple: [2007 NRL season, DallyMPosition, halfback]
-
A.
draftPosition
Indicates the selection order or specific pick at which an entity (such as a player) was chosen in a draft process.
-
B.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
C.
relativePositionInStadium
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
-
D.
locationPosed
Indicates that an entity is positioned or situated at a specific location.
-
E.
positionInLineup
Indicates the specific ordered place an entity occupies within a lineup or sequence of entities.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1be5a8081909bf727e28a5bba4a |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:22 a.m.