Triple
T35603439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barmer basin |
E1028816
|
entity |
| Predicate | primaryTrapType |
P31461
|
FINISHED |
| Object | structural traps |
—
|
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: structural traps | Statement: [Barmer basin, primaryTrapType, structural traps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTrapType Context triple: [Barmer basin, primaryTrapType, structural traps]
-
A.
trapType
chosen
Indicates the specific kind or category of trap associated with an entity or situation.
-
B.
primaryCatch
Indicates that an entity is the main or most significant target, recipient, or object captured or obtained in a given context.
-
C.
primaryEventType
Indicates the main or most significant category of event with which an entity, record, or occurrence is primarily associated.
-
D.
primaryContainmentType
Indicates the main method or structure used to hold, enclose, or confine one entity within another.
-
E.
primaryDetectorType
Indicates the main kind or category of detector that is used as the primary sensing or measurement component in a given context.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.