Triple
T15468831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julien Dubuque |
E372100
|
entity |
| Predicate | workedWithResource |
P118354
|
FINISHED |
| Object | lead ore |
—
|
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: lead ore | Statement: [Julien Dubuque, workedWithResource, lead ore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedWithResource Context triple: [Julien Dubuque, workedWithResource, lead ore]
-
A.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
-
B.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
C.
workUsedAs
Indicates that one work is employed or utilized in the creation, performance, or presentation of another work.
-
D.
workedUnder
Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority of another entity.
-
E.
workUsedFor
Indicates that a particular work (such as a document, artwork, or dataset) is employed or utilized for a specific purpose, task, or function.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f69a31c81909a749247b6615d91 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:33 a.m.