Triple
T7711121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. A. L. Waddell |
E174752
|
entity |
| Predicate | publishedInField |
P1753
|
FINISHED |
| Object | bridge engineering |
—
|
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: bridge engineering | Statement: [J. A. L. Waddell, publishedInField, bridge engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedInField Context triple: [J. A. L. Waddell, publishedInField, bridge engineering]
-
A.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
-
B.
fieldOfPublication
chosen
Indicates the academic or topical area in which a work is published.
-
C.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
D.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
E.
publishedInPart
Indicates that a work or content item was released or made available only as a portion or installment within a larger publication or series.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.