Triple
T38491728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devil's Nose |
E918069
|
entity |
| Predicate | hasEngineeringTechnique |
P3047
|
FINISHED |
| Object | cut-and-fill excavation |
—
|
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: cut-and-fill excavation | Statement: [Devil's Nose, hasEngineeringTechnique, cut-and-fill excavation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEngineeringTechnique Context triple: [Devil's Nose, hasEngineeringTechnique, cut-and-fill excavation]
-
A.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering entity.
-
C.
hasEngineeringFunction
Indicates that an entity possesses or performs a specific engineering-related role, purpose, or operational function.
-
D.
hasEngineeringStyle
Indicates that an entity possesses or exhibits a particular engineering approach, methodology, or design style in how it is created, structured, or operates.
-
E.
hasEngineeringSignificance
Indicates that something holds notable importance, impact, or relevance within an engineering context or for engineering activities.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: May 3, 2026, 4:31 p.m.