Triple
T1351877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghaghara |
E28899
|
entity |
| Predicate | dischargeType |
P26897
|
FINISHED |
| Object | perennial |
—
|
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: perennial | Statement: [Ghaghara, dischargeType, perennial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dischargeType Context triple: [Ghaghara, dischargeType, perennial]
-
A.
hasDischarge
Indicates that one entity releases, emits, or expels a substance, energy, or flow from itself.
-
B.
dischargeRank
Indicates the rank or status an individual held at the time they were discharged from a role, service, or organization.
-
C.
dischargeLocation
Indicates the place or facility where an entity (such as a person, object, or substance) is released, sent, or discharged to after a prior state or process.
-
D.
dischargeRanking
Indicates the relative level or position of an entity in an ordered list based on the amount or rate of discharge (such as emissions, effluents, or released substances).
-
E.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
- F. None of above. chosen
Provenance (4 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26b1b4881908ae4b1b2c9b268a0 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:56 p.m.