Triple
T14117932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodney McMullen |
E339821
|
entity |
| Predicate | startPositionAtKroger |
P112881
|
FINISHED |
| Object | part-time stock clerk |
—
|
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: part-time stock clerk | Statement: [Rodney McMullen, startPositionAtKroger, part-time stock clerk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startPositionAtKroger Context triple: [Rodney McMullen, startPositionAtKroger, part-time stock clerk]
-
A.
slotLocation
Indicates the specific position or compartment within a larger container or system where an item is placed or assigned.
-
B.
openedFirstHypermarket
Indicates that the subject entity was the first to open a hypermarket for the object entity or within the context specified.
-
C.
startPointLocatedIn
Indicates that the starting point of something is geographically or spatially located within a specified area or region.
-
D.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
-
E.
currentPosition
Indicates the present role, job, or status an entity currently holds within a given context.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de609322ac8190bb389ca250882af5 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.