Triple
T3631509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kotri Barrage |
E76964
|
entity |
| Predicate | engineeringClassification |
P6736
|
FINISHED |
| Object | major barrage |
—
|
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: major barrage | Statement: [Kotri Barrage, engineeringClassification, major barrage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeringClassification Context triple: [Kotri Barrage, engineeringClassification, major barrage]
-
A.
researchClassification
Indicates that an entity is assigned a specific category or type within a research-related classification scheme.
-
B.
definesClassification
Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
-
C.
classificationSystem
chosen
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
D.
classificationByUS
Indicates a relationship where an entity is assigned a category, status, or type according to a classification system defined or used by the United States.
-
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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30136e88190922bb542971b5239 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.