Triple
T4478672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lathrop Douglass |
E100072
|
entity |
| Predicate | hasWorkOn |
P56793
|
FINISHED |
| Object | public infrastructure |
—
|
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: public infrastructure | Statement: [Lathrop Douglass, hasWorkOn, public infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkOn Context triple: [Lathrop Douglass, hasWorkOn, public infrastructure]
-
A.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
B.
hasWorkAsSubject
Indicates that an entity serves as the subject (creator or originator) of a particular work or creative output.
-
C.
hasWorkSubject
Indicates that a work (such as a document, artwork, or project) is about or concerns a particular subject or topic.
-
D.
hasWorkDedicatedTo
Indicates that one entity has a work (such as a book, artwork, or composition) that is formally dedicated to another entity.
-
E.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
| PDg | Predicate description generation | batch_69b35727a8ac819090420bd3e2cfbcf1 |
completed | March 13, 2026, 12:15 a.m. |
Created at: March 12, 2026, 11:35 p.m.