Triple
T24885369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bindon Blood Stoney |
E622832
|
entity |
| Predicate | usedEngineeringMethod |
P625
|
FINISHED |
| Object | heavy lifting appliances for harbor works |
—
|
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: heavy lifting appliances for harbor works | Statement: [Bindon Blood Stoney, usedEngineeringMethod, heavy lifting appliances for harbor works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedEngineeringMethod Context triple: [Bindon Blood Stoney, usedEngineeringMethod, heavy lifting appliances for harbor works]
-
A.
engineeringBasis
Indicates that something serves as the foundational technical or engineering rationale, justification, or underlying basis for another entity or decision.
-
B.
engineeringContribution
Indicates a relationship where an entity contributes engineering work, expertise, or effort toward the design, development, or improvement of another entity.
-
C.
hasEngineeringSignificance
Indicates that something holds notable importance, impact, or relevance within an engineering context or for engineering activities.
-
D.
constructionMethod
chosen
Indicates the technique or process by which something is built, assembled, or created.
-
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.
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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:25 a.m.