Triple
T30034829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East India Company ships |
E763124
|
entity |
| Predicate | typicalRig |
P21966
|
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: [East India Company ships, typicalRig, full-rigged ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRig Context triple: [East India Company ships, typicalRig, full-rigged ship]
-
A.
typeOfRig
chosen
Indicates the specific kind or configuration of rig used or associated with an entity.
-
B.
rigging
Indicates the act of manipulating or tampering with a process, system, or outcome to unfairly influence the result.
-
C.
typeOfRigging
Indicates the kind or configuration of rigging used in relation to an object or structure.
-
D.
typicalGear
Indicates that the object represents the usual or standard equipment or gear commonly associated with the subject.
-
E.
typicalRegister
Indicates the usual or most common linguistic register (e.g., formal, informal, technical) in which something—such as a word, expression, or communication—is typically used.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0338d1074481909541e6150307e7f8 |
completed | May 12, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a03386e7da08190b533cb0e908503dd |
completed | May 12, 2026, 2:25 p.m. |
Created at: April 29, 2026, 6:50 p.m.