Triple
T14801494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamuna River (historical feed via aqueducts and channels) |
E347920
|
entity |
| Predicate | usedEngineeringForm |
P26269
|
FINISHED |
| Object | aqueducts |
—
|
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: aqueducts | Statement: [Yamuna River (historical feed via aqueducts and channels), usedEngineeringForm, aqueducts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedEngineeringForm Context triple: [Yamuna River (historical feed via aqueducts and channels), usedEngineeringForm, aqueducts]
-
A.
constructionForm
Indicates the method, style, or structural technique by which something is built or constructed.
-
B.
usesForm
chosen
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
-
C.
employsForm
Indicates that an entity makes use of or applies a particular form or format in carrying out an action or function.
-
D.
engineeringStandard
Indicates that something conforms to, is defined by, or is governed by a specified engineering standard or set of technical norms.
-
E.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd62c36c81909c2993dc7d1a79ea |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.