Triple
T27076166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nore |
E685466
|
entity |
| Predicate | navalStationStatus |
P82902
|
FINISHED |
| Object | former Royal Navy command |
—
|
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: former Royal Navy command | Statement: [The Nore, navalStationStatus, former Royal Navy command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalStationStatus Context triple: [The Nore, navalStationStatus, former Royal Navy command]
-
A.
navyListStatus
Indicates the status or classification of an entity within a navy’s official list or registry.
-
B.
militaryBaseStatus
chosen
Indicates the operational condition or readiness state of a military base at a given time.
-
C.
navalPowerStatus
Indicates the relative strength, capability, or strategic standing of an entity’s naval forces compared to others or to defined benchmarks.
-
D.
navalFacilityName
Indicates that a naval facility is associated with a specific proper name or designation.
-
E.
hasNavalFacility
Indicates that one entity possesses, hosts, or contains a naval facility (such as a naval base, port, or installation) associated with it.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 8:31 a.m.