Triple
T24200184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outward Bound |
E599952
|
entity |
| Predicate | programEnvironment |
P155154
|
FINISHED |
| Object | wilderness settings |
—
|
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: wilderness settings | Statement: [Outward Bound, programEnvironment, wilderness settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programEnvironment Context triple: [Outward Bound, programEnvironment, wilderness settings]
-
A.
programContext
Indicates the situational or environmental conditions (such as scope, settings, or surrounding code) within which a program or computational process is defined or executed.
-
B.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
C.
productionEnvironment
Indicates that something is part of, deployed to, or operating within a live production environment as opposed to a test or development setting.
-
D.
environmentVariable
Indicates that one entity is an environment variable associated with, defined for, or used by another entity (such as a process, application, or system).
-
E.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca08874819081dd6613ac462c40 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:36 p.m.