Triple
T29084713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wheeler Shipbuilding |
E734073
|
entity |
| Predicate | builtVessel |
P92486
|
FINISHED |
| Object | Granma |
—
|
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: Granma | Statement: [Wheeler Shipbuilding, builtVessel, Granma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtVessel Context triple: [Wheeler Shipbuilding, builtVessel, Granma]
-
A.
vesselBuilder
chosen
Indicates that one entity is the builder, manufacturer, or constructor of a vessel associated with another entity.
-
B.
namedVesselOf
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
-
C.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
-
D.
vesselLaunched
Indicates that a vessel has been formally set afloat or put into operation at a specific time or place.
-
E.
hasVessel
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 10:59 a.m.