Triple
T181176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastham Lock |
E3878
|
entity |
| Predicate | hasEngineeringDiscipline |
P592
|
FINISHED |
| Object | civil 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: civil engineering | Statement: [Eastham Lock, hasEngineeringDiscipline, civil engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngineeringDiscipline Context triple: [Eastham Lock, hasEngineeringDiscipline, civil engineering]
-
A.
associatedWithDiscipline
chosen
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
-
B.
hasTechnicalSociety
Indicates that an entity is associated with, or possesses membership in, a technical or engineering-focused society or organization.
-
C.
hasFaculty
Indicates that an institution or department possesses or is associated with one or more faculty members.
-
D.
chiefEngineer
Indicates that one entity serves as the primary or lead engineer responsible for overseeing engineering activities for another entity.
-
E.
hasDoctoralProgram
Indicates that an institution or academic unit offers and administers a doctoral-level degree program.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25923507c8190bd7f6eda404b0da0 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.