Triple
T35660859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEPP |
E1030429
|
entity |
| Predicate | associatedWithVesselClass |
P11978
|
FINISHED |
| Object | Healy-class icebreaker |
E1030427
|
NE 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: Healy-class icebreaker | Statement: [NEPP, associatedWithVesselClass, Healy-class icebreaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithVesselClass Context triple: [NEPP, associatedWithVesselClass, Healy-class icebreaker]
-
A.
isVesselFor
Indicates that one entity functions as a container or medium specifically used to hold, carry, or convey another entity.
-
B.
hasVesselType
chosen
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
C.
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.
-
D.
appliesToVesselName
Indicates that something (such as a rule, condition, or record) is specifically associated with or relevant to a particular vessel’s name.
-
E.
supportsClassOfShip
Indicates that one entity is capable of accommodating, servicing, or otherwise functionally supporting a specified class of ship.
- F. None of above.
Provenance (4 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38727fb4cc8190b1b2261d89e0071d |
completed | June 21, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.