Triple
T3524700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago SRW wheat |
E74508
|
entity |
| Predicate | hasEndUser |
P6943
|
FINISHED |
| Object | millers |
—
|
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: millers | Statement: [Chicago SRW wheat, hasEndUser, millers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndUser Context triple: [Chicago SRW wheat, hasEndUser, millers]
-
A.
hasUser
chosen
Indicates that an entity is associated with or linked to a specific user.
-
B.
hasUserService
Indicates that an entity is associated with or utilizes a particular user-related service.
-
C.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
D.
hasEndorser
Indicates that one entity supports, approves, or publicly backs another entity, typically lending it credibility or validation.
-
E.
hasVIPTerminal
Indicates that one entity possesses or provides access to a VIP (very important person) terminal associated with 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc68b15881909b407486946ec3c5 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.