Triple
T34981063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Happy Return |
E1008814
|
entity |
| Predicate | protagonistShip |
P35755
|
FINISHED |
| Object | HMS Lydia |
—
|
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: HMS Lydia | Statement: [The Happy Return, protagonistShip, HMS Lydia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistShip Context triple: [The Happy Return, protagonistShip, HMS Lydia]
-
A.
primaryAntagonistShip
Indicates that one ship serves as the main opposing or enemy vessel in relation to another entity or context.
-
B.
targetedShip
Indicates that one entity has selected or designated a particular ship as the focus of its attention or action, such as for attack, tracking, or interaction.
-
C.
mainShip
chosen
Indicates that one entity serves as the primary or principal ship associated with another entity.
-
D.
protagonistHouseboatName
Indicates the name assigned to the houseboat that belongs to or is used by the protagonist.
-
E.
capturedShip
Indicates that one party has taken control of another party's ship, typically by force or seizure.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.