Triple
T17752734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QBism |
E443151
|
entity |
| Predicate | treatsOutcomeAs |
P128203
|
FINISHED |
| Object | experience registered by the agent |
—
|
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: experience registered by the agent | Statement: [QBism, treatsOutcomeAs, experience registered by the agent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsOutcomeAs Context triple: [QBism, treatsOutcomeAs, experience registered by the agent]
-
A.
governsOutcome
Indicates that one entity has decisive control or influence over the result or consequence affecting another entity.
-
B.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
C.
describesOutcomeOf
Indicates that one entity specifies or characterizes the result, consequence, or outcome produced by another entity or process.
-
D.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
E.
treatsRightAs
Indicates that one entity provides medical or therapeutic treatment to another entity who is identified as the right-hand participant in the relationship.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841c0540819093a32d759775c61f |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3cfab7edc8190b663282d565a0389 |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:10 a.m.