Triple
T34981076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Happy Return |
E1008814
|
entity |
| Predicate | internalChronologyOrder |
P152018
|
FINISHED |
| Object | later than Mr. Midshipman Hornblower |
—
|
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: later than Mr. Midshipman Hornblower | Statement: [The Happy Return, internalChronologyOrder, later than Mr. Midshipman Hornblower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalChronologyOrder Context triple: [The Happy Return, internalChronologyOrder, later than Mr. Midshipman Hornblower]
-
A.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
B.
chronologicallyOrders
Indicates that one entity arranges or sequences other entities according to their positions in time, from earlier to later.
-
C.
singleChronology
Indicates that the entities participate in or are associated with exactly one chronological sequence or timeline, without parallel or branching temporal orders.
-
D.
involvesChronology
Indicates that the relationship or action explicitly depends on, references, or organizes events according to their order or position in time.
-
E.
chronologicalOrderInList
chosen
Indicates that one item appears before another in the temporal sequence defined by a specific list or ordered collection.
- 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_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: May 3, 2026, 4:01 p.m.