Triple
T25842312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attack-class submarine |
E650968
|
entity |
| Predicate | intendedConstructionSite |
P6549
|
FINISHED |
| Object | Osborne Naval Shipyard |
—
|
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: Osborne Naval Shipyard | Statement: [Attack-class submarine, intendedConstructionSite, Osborne Naval Shipyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedConstructionSite Context triple: [Attack-class submarine, intendedConstructionSite, Osborne Naval Shipyard]
-
A.
constructionSite
chosen
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.
plannedFacility
Indicates that a facility is intended or scheduled to be built, established, or implemented in the future but does not yet exist or operate.
-
D.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
E.
intendedBuildingType
Indicates the type of building that something is planned or designed to be.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 22, 2026, 7:50 a.m.