Triple
T28892901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Carter |
E732751
|
entity |
| Predicate | riskLevelInNarrative |
P3842
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Adam Carter, riskLevelInNarrative, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskLevelInNarrative Context triple: [Adam Carter, riskLevelInNarrative, high]
-
A.
riskLevel
chosen
Indicates the degree of potential harm, loss, or adverse outcome associated with a particular situation, action, or entity.
-
B.
riskProfileClaim
Indicates that a claim is being made about the level or characteristics of risk associated with an entity or situation.
-
C.
riskDescription
Indicates a textual explanation of the nature, causes, and potential impact of a specific risk.
-
D.
riskHighlighted
Indicates that a particular risk has been identified and specially marked for attention or emphasis.
-
E.
riskDepicted
Indicates that a representation (such as an image, text, or symbol) portrays, illustrates, or conveys the presence or possibility of a particular risk.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa137ec8190b0ccb5ab15981e5a |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:56 a.m.