Triple
T36806243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candida Morell |
E909459
|
entity |
| Predicate | makesChoiceBetween |
P54688
|
FINISHED |
| Object | James Morell |
—
|
NE NERFINISHED |
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: James Morell | Statement: [Candida Morell, makesChoiceBetween, James Morell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesChoiceBetween Context triple: [Candida Morell, makesChoiceBetween, James Morell]
-
A.
madeChoiceBetween
chosen
Indicates that an entity selected one option from among two or more specified alternatives.
-
B.
requiresChoiceBetween
Indicates that one must select between two or more specified options, and that making such a choice is necessary in the given context.
-
C.
coordinateChoice
Indicates that one option is selected from a set of mutually exclusive alternatives within a coordinated choice structure.
-
D.
canChoose
Indicates that an entity has the ability or permission to select one option or entity from among alternatives.
-
E.
decisionMakingTool
Indicates that an entity functions as a tool or system used to support, structure, or carry out decision-making processes for another entity.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.