Triple
T35191364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ned Schneebly |
E1016126
|
entity |
| Predicate | jobUsedBy |
P93910
|
FINISHED |
| Object | Dewey Finn |
—
|
NE NERFINISHED |
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: Dewey Finn | Statement: [Ned Schneebly, jobUsedBy, Dewey Finn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jobUsedBy Context triple: [Ned Schneebly, jobUsedBy, Dewey Finn]
-
A.
usedInWorkBy
Indicates that something (such as a method, material, or concept) is employed or incorporated within a work created by a particular agent or author.
-
B.
hasWorkUsedBy
Indicates that a work (such as a resource, document, or artifact) is utilized or referenced by another entity in performing its activities or functions.
-
C.
workUsedFor
Indicates that a particular work (such as a document, artwork, or dataset) is employed or utilized for a specific purpose, task, or function.
-
D.
workUsedAs
Indicates that one work is employed or utilized in the creation, performance, or presentation of another work.
-
E.
workFor
chosen
Indicates that one entity is employed by or performs work under the authority or direction of 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dc8627c8190b19f34a1019a30f1 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.