Triple
T38610963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Mayo |
E934475
|
entity |
| Predicate | makesChoice |
P54688
|
FINISHED |
| Object | abandons dream of going to sea |
—
|
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: abandons dream of going to sea | Statement: [Robert Mayo, makesChoice, abandons dream of going to sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesChoice Context triple: [Robert Mayo, makesChoice, abandons dream of going to sea]
-
A.
madeChoiceBetween
chosen
Indicates that an entity selected one option from among two or more specified alternatives.
-
B.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
C.
canChoose
Indicates that an entity has the ability or permission to select one option or entity from among alternatives.
-
D.
coordinateChoice
Indicates that one option is selected from a set of mutually exclusive alternatives within a coordinated choice structure.
-
E.
decisionQuest
Indicates that an entity is faced with or engaged in making a significant choice or judgment, often involving uncertainty or multiple possible outcomes.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.