Triple
T37104652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAST |
E918808
|
entity |
| Predicate | siteSelectionReason |
P30171
|
FINISHED |
| Object | karst depression terrain |
—
|
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: karst depression terrain | Statement: [FAST, siteSelectionReason, karst depression terrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteSelectionReason Context triple: [FAST, siteSelectionReason, karst depression terrain]
-
A.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
B.
hostCountrySelectionReason
Indicates the reason or criteria for which a particular country was chosen to host an event, activity, or entity.
-
C.
reasonForLocation
chosen
Indicates the cause, purpose, or justification for why an entity is at a particular location.
-
D.
listingReason
Indicates the reason or justification for why an item, entity, or subject has been listed or included in a particular collection, catalog, or context.
-
E.
reasonForInstallation
Indicates the underlying purpose, cause, or justification for why something was installed.
- 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.