Triple
T34011905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirate Lords |
E872136
|
entity |
| Predicate | governTerritory |
P10006
|
FINISHED |
| Object | Caribbean Sea |
—
|
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: Caribbean Sea | Statement: [Pirate Lords, governTerritory, Caribbean Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governTerritory Context triple: [Pirate Lords, governTerritory, Caribbean Sea]
-
A.
governedTerritory
chosen
Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
-
B.
governedTerritoryWith
Indicates that one entity exercised governing authority or control over a specified territory, region, or domain in association with another entity.
-
C.
governedTerritoryVia
Indicates a relationship where an authority or governing body exercises control over a territory through an intermediary entity, mechanism, or arrangement.
-
D.
governingBodyTerritory
Indicates the territory or geographic area over which a governing body has authority or jurisdiction.
-
E.
missionTerritoryOf
Indicates that a specified territory is under the jurisdiction or scope of a particular mission.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00c9ddd62881909859a36b114a4132 |
completed | May 10, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a00c939b88881909d5353db4265e572 |
completed | May 10, 2026, 6:06 p.m. |
Created at: May 1, 2026, 1:51 a.m.