Triple
T23600248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revenge (English galleon) |
E582729
|
entity |
| Predicate | constructionPlace |
P14101
|
FINISHED |
| Object | Plymouth shipyards |
—
|
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: Plymouth shipyards | Statement: [Revenge (English galleon), constructionPlace, Plymouth shipyards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionPlace Context triple: [Revenge (English galleon), constructionPlace, Plymouth shipyards]
-
A.
constructionSite
Indicates that an entity is a location or area where construction work is actively taking place or is planned to occur.
-
B.
buildingInvolved
Indicates that a particular building participates in, is affected by, or is otherwise relevant to the specified event or relationship.
-
C.
placeBuilt
chosen
Indicates that a structure or facility was constructed at a specific location.
-
D.
constructionBase
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
E.
constructionDirection
Indicates the orientation or path along which a structure is built or assembled.
- 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0936f588190aead4419aedfcb0e |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:43 p.m.