Triple
T3391584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deliverance |
E71431
|
entity |
| Predicate | constructedAfterEvent |
P3117
|
FINISHED |
| Object | 1609 wreck of Sea Venture |
—
|
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: 1609 wreck of Sea Venture | Statement: [Deliverance, constructedAfterEvent, 1609 wreck of Sea Venture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructedAfterEvent Context triple: [Deliverance, constructedAfterEvent, 1609 wreck of Sea Venture]
-
A.
createdAfterEvent
chosen
Indicates that the creation of one entity occurred after a specified event in time.
-
B.
constructedDuring
Indicates that one entity was built or created within the time period defined by another entity or event.
-
C.
constructedAs
Indicates that one entity is built, formed, or created in the manner, structure, or configuration specified by another entity.
-
D.
constructedUnder
Indicates that something was built, created, or assembled while subject to the authority, direction, or conditions imposed by a particular agent, rule, plan, or regime.
-
E.
classAfter
Indicates that one class or course occurs later in time or sequence than another class or course.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb850594c81909b6f8a384fc98cb2 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.