Triple
T37104734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawodang depression |
E918810
|
entity |
| Predicate | selectionReasonForFAST |
P3364
|
FINISHED |
| Object | radio-quiet environment |
—
|
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: radio-quiet environment | Statement: [Dawodang depression, selectionReasonForFAST, radio-quiet environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionReasonForFAST Context triple: [Dawodang depression, selectionReasonForFAST, radio-quiet environment]
-
A.
selectionReason
chosen
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
B.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
C.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
D.
reasonForExecution
Indicates that one entity specifies the cause, motive, or justification for carrying out the execution of another entity or action.
-
E.
selectionDescribedIn
Indicates that a particular selection or choice is documented, explained, or detailed within a specified description or source.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.