Triple
T32619843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle at the Ramelle bridge |
E833890
|
entity |
| Predicate | chronologicallyOccursAt |
P89854
|
FINISHED |
| Object | climax of Saving Private Ryan |
—
|
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: climax of Saving Private Ryan | Statement: [Battle at the Ramelle bridge, chronologicallyOccursAt, climax of Saving Private Ryan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyOccursAt Context triple: [Battle at the Ramelle bridge, chronologicallyOccursAt, climax of Saving Private Ryan]
-
A.
chronologicalPoint
chosen
Indicates that something is associated with, occurs at, or is anchored to a specific point in time within a chronological sequence.
-
B.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
C.
chronologicallyInvolvedIn
Indicates that an entity participates in or is associated with an event, process, or activity during a specific time period in a chronological sequence.
-
D.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
E.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 1:06 a.m.