Triple
T8754793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Royal (Acadia) |
E208046
|
entity |
| Predicate | captureEvent |
P85202
|
FINISHED |
| Object | 1710 capture of Port Royal |
—
|
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: 1710 capture of Port Royal | Statement: [Port Royal (Acadia), captureEvent, 1710 capture of Port Royal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captureEvent Context triple: [Port Royal (Acadia), captureEvent, 1710 capture of Port Royal]
-
A.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
B.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
C.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
-
D.
coordinateEvent
Indicates overseeing and organizing the planning, logistics, and execution of an event in collaboration with involved parties.
-
E.
peakEvent
Indicates the occurrence of a maximum or most intense point within a process, activity, or measurable phenomenon.
- F. None of above. chosen
Provenance (4 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dd83088819082cf54adc0c04243 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:39 p.m.