Triple
T38231877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAE |
E1013510
|
entity |
| Predicate | possibleCEFROutcome |
P52041
|
FINISHED |
| Object | B2 |
—
|
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: B2 | Statement: [CAE, possibleCEFROutcome, B2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleCEFROutcome Context triple: [CAE, possibleCEFROutcome, B2]
-
A.
canonicalOutcome
Indicates that an event, process, or interaction leads to its standard, primary, or officially recognized result or consequence.
-
B.
supportedOutcomeOf
Indicates that one entity serves as evidence, backing, or justification for the outcome or result represented by another entity.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
maySucceed
Indicates that one entity has the potential or possibility to follow or replace another in a role, position, or sequence.
-
E.
possibleJudgment
chosen
Indicates a potential or anticipated judgment, decision, or evaluative outcome that could be made about an entity or situation.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.