Triple
T37700011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibraltar fortress artillery |
E939031
|
entity |
| Predicate | notableCalibre |
P204347
|
FINISHED |
| Object | 9.2‑inch coastal guns |
—
|
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: 9.2‑inch coastal guns | Statement: [Gibraltar fortress artillery, notableCalibre, 9.2‑inch coastal guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCalibre Context triple: [Gibraltar fortress artillery, notableCalibre, 9.2‑inch coastal guns]
-
A.
notableLibrary
Indicates that the subject is a library recognized for its significance, prominence, or special importance.
-
B.
calibre
Indicates the quality, capability, or degree of excellence associated with an entity in relation to others.
-
C.
notableReader
Indicates that the subject is recognized as a particularly significant or distinguished reader of the object.
-
D.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
-
E.
notableStore
Indicates that a store is recognized as notable or significant in some context (e.g., historically, culturally, or commercially).
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.