Triple
T36031771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osborne |
E1042279
|
entity |
| Predicate | industrialFacility |
P25392
|
FINISHED |
| Object | shipbuilding facilities |
—
|
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: shipbuilding facilities | Statement: [Osborne, industrialFacility, shipbuilding facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialFacility Context triple: [Osborne, industrialFacility, shipbuilding facilities]
-
A.
hasIndustrialPlant
chosen
Indicates that an entity possesses, operates, or is associated with an industrial plant facility.
-
B.
hasProductionFacilitiesIn
Indicates that an entity operates or owns production facilities located within a specified geographic area or jurisdiction.
-
C.
nearbyIndustrialInstallation
Indicates that one entity is located close to an industrial facility or installation.
-
D.
productionFacilityType
Indicates the specific kind or category of facility where production or manufacturing activities take place.
-
E.
industrialComplex
Indicates a relationship where a facility or site functions as a large-scale, integrated center for industrial production, processing, or related 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.