Triple
T30914396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortress of Port Royal |
E787538
|
entity |
| Predicate | afterCaptureKnownAs |
P89074
|
FINISHED |
| Object | Fortress of Annapolis Royal |
—
|
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: Fortress of Annapolis Royal | Statement: [Fortress of Port Royal, afterCaptureKnownAs, Fortress of Annapolis Royal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterCaptureKnownAs Context triple: [Fortress of Port Royal, afterCaptureKnownAs, Fortress of Annapolis Royal]
-
A.
afterCapture
Indicates that one event or state occurs subsequent to the act of capturing something.
-
B.
afterConversionKnownAs
chosen
Indicates that an entity is referred to by a new name or identifier after undergoing a conversion or transformation.
-
C.
capturedAfter
Indicates that one entity is captured at a point in time later than the capture of another entity.
-
D.
afterAcquisitionName
Indicates that the object entity represents the name used by a company or organization after it has been acquired.
-
E.
capturedAs
Indicates that one entity has been taken into custody or control by another entity, typically as a prisoner or target.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 8:51 p.m.