Triple
T36348729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish ship Santísima Trinidad |
E895135
|
entity |
| Predicate | typeOfKeel |
P8584
|
FINISHED |
| Object | full-rigged ship |
—
|
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: full-rigged ship | Statement: [Spanish ship Santísima Trinidad, typeOfKeel, full-rigged ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfKeel Context triple: [Spanish ship Santísima Trinidad, typeOfKeel, full-rigged ship]
-
A.
hasKeel
Indicates that an entity possesses a keel as a structural or anatomical feature.
-
B.
keelLaidFor
Indicates that the initial structural construction (keel laying) of a vessel has been formally started for a particular ship or project.
-
C.
hullType
chosen
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
-
D.
hasSailType
Indicates that an entity is characterized by or equipped with a specific type of sail.
-
E.
rudderType
Indicates the specific kind or configuration of rudder associated with an object or system.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a02fcbe03d0819082d3dd715ed41623 |
completed | May 12, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_6a02fc62138081908d2dbc5db7541d13 |
completed | May 12, 2026, 10:09 a.m. |
Created at: May 3, 2026, 4:09 p.m.