Triple
T11094236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Level Main Drain |
E262333
|
entity |
| Predicate | engineeringPurpose |
P49728
|
FINISHED |
| Object | protect settlements from flooding |
—
|
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: protect settlements from flooding | Statement: [Middle Level Main Drain, engineeringPurpose, protect settlements from flooding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeringPurpose Context triple: [Middle Level Main Drain, engineeringPurpose, protect settlements from flooding]
-
A.
engineeringGoal
chosen
Indicates that an entity has a specific engineering-related objective, target, or desired outcome it is intended to achieve or support.
-
B.
engineeringEmphasis
Indicates that something places a primary focus or specialization on engineering principles, methods, or activities.
-
C.
engineeringFeature
Indicates that one entity serves as an engineering-related feature, component, or characteristic of another entity within a technical or designed system.
-
D.
purposeOfConstruction
Indicates that one entity was constructed or built in order to serve, enable, or fulfill the function, goal, or intended use represented by another entity.
-
E.
engineeringFeats
Indicates that one entity is recognized for notable engineering achievements, constructions, or technical accomplishments associated with another entity.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0783e88190aae3d461730c2d70 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.