Triple
T9265665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powdr Corporation |
E222692
|
entity |
| Predicate | typeOfFacilitiesOperated |
P43750
|
FINISHED |
| Object | terrain parks |
—
|
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: terrain parks | Statement: [Powdr Corporation, typeOfFacilitiesOperated, terrain parks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFacilitiesOperated Context triple: [Powdr Corporation, typeOfFacilitiesOperated, terrain parks]
-
A.
operatesFacility
Indicates that an entity is responsible for running, managing, or controlling the operations of a particular facility.
-
B.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
C.
venueTypeOperated
chosen
Indicates that an entity operates or manages a venue of a specified type.
-
D.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
E.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
- 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_69ca841f2e808190a64f4c31903a1332 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0749efb8819083b48e7446e84a06 |
completed | April 1, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.