Triple
T38330498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry DeWolf-class |
E1037807
|
entity |
| Predicate | boatCapability |
P190649
|
FINISHED |
| Object | multiple RHIBs |
—
|
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: multiple RHIBs | Statement: [Harry DeWolf-class, boatCapability, multiple RHIBs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatCapability Context triple: [Harry DeWolf-class, boatCapability, multiple RHIBs]
-
A.
canRideBoat
Indicates that an entity has the ability or permission to travel using a boat.
-
B.
boatTypeAllowed
Indicates that a specified type of boat is permitted or authorized in a given context or location.
-
C.
boatRole
Indicates the specific function, duty, or position an entity has in relation to a boat within a given context.
-
D.
hasBoatCapacity
Indicates the maximum number of people or amount of load that a boat is designed or allowed to carry.
-
E.
boatConfiguration
Indicates the specific arrangement, layout, or setup of components or features on a boat.
- F. None of above. chosen
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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.