Triple
T10951960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Royal |
E258745
|
entity |
| Predicate | navalHistory |
P96804
|
FINISHED |
| Object | Royal Navy station |
—
|
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: Royal Navy station | Statement: [Port Royal, navalHistory, Royal Navy station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalHistory Context triple: [Port Royal, navalHistory, Royal Navy station]
-
A.
navalEra
Indicates the historical period or era in which a naval-related event, activity, or condition takes place.
-
B.
navalDiscipline
Indicates the enforcement or maintenance of rules, order, and conduct within a naval or maritime context.
-
C.
navalOpposition
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
-
D.
navalAnalogue
Indicates that one entity serves as the naval or maritime counterpart or equivalent of another entity in function, role, or classification.
-
E.
navalDoctrineImpact
Indicates how a particular naval doctrine influences or alters the effectiveness, behavior, or outcomes of naval forces or operations.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770fcfb3c8190b7823869670184a6 |
completed | April 9, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d7322370648190ba14cdd6fb4cdcb0 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:23 p.m.