Triple
T24959058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CL-47 |
E624552
|
entity |
| Predicate | hasHullCode |
P105180
|
FINISHED |
| Object | CL |
—
|
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: CL | Statement: [CL-47, hasHullCode, CL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHullCode Context triple: [CL-47, hasHullCode, CL]
-
A.
hasHullType
Indicates that an entity possesses or is characterized by a specific type or form of hull.
-
B.
associatedWithHullName
chosen
Indicates a relationship where something is linked or connected to a specific hull name, typically identifying the vessel or structure it belongs to.
-
C.
hasBorderCode
Indicates that there is an associated code or identifier specifying the type or status of a border between entities.
-
D.
hullFeature
Indicates a physical characteristic, structure, or component that is part of or present on the hull of an object (typically a vehicle or vessel).
-
E.
usedHullNumberSystem
Indicates that an entity employed a hull numbering system to identify or classify ships or vessels.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490283c481908c18246dc7125eec |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:58 a.m.