Triple
T31190072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial and Royal War Navy |
E795153
|
entity |
| Predicate | shipbuildingCenter |
P4334
|
FINISHED |
| Object | Trieste |
—
|
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: Trieste | Statement: [Imperial and Royal War Navy, shipbuildingCenter, Trieste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipbuildingCenter Context triple: [Imperial and Royal War Navy, shipbuildingCenter, Trieste]
-
A.
shipbuildingActivity
Indicates the activity or process of constructing, assembling, or significantly modifying ships or large watercraft.
-
B.
shipbuilder
Indicates that one entity is the builder or constructor of a ship associated with another entity.
-
C.
shipyard
chosen
Indicates a relationship where a location functions as a facility for building, repairing, or maintaining ships.
-
D.
shipyardLocatedOn
Indicates that a shipyard is situated on or within the geographic area of a specified landmass, coastline, or body of water.
-
E.
shipyardArea
Indicates the total physical area occupied or used by a shipyard for its operations.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.