Triple
T24416543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chirk Aqueduct |
E615598
|
entity |
| Predicate | coEngineer |
P155840
|
FINISHED |
| Object | William Jessop |
—
|
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: William Jessop | Statement: [Chirk Aqueduct, coEngineer, William Jessop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coEngineer Context triple: [Chirk Aqueduct, coEngineer, William Jessop]
-
A.
laterEngineer
Indicates that one entity becomes an engineer at a later time than another entity.
-
B.
engineeringContribution
Indicates a relationship where an entity contributes engineering work, expertise, or effort toward the design, development, or improvement of another entity.
-
C.
engineeringBasis
Indicates that something serves as the foundational technical or engineering rationale, justification, or underlying basis for another entity or decision.
-
D.
chiefEngineer
Indicates that one entity serves as the primary or lead engineer responsible for overseeing engineering activities for another entity.
-
E.
engineeringDesign
Indicates the relationship in which an entity is responsible for planning, specifying, or creating the technical design of another entity (such as a system, component, or structure).
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958645248190a22bd0b8bcc2dfe2 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f2915233c48190a181c8c1924e892c |
completed | April 29, 2026, 11:16 p.m. |
Created at: April 18, 2026, 2:13 a.m.