Triple
T8882024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rauma-class fast attack craft |
E211433
|
entity |
| Predicate | hasDraught |
P85505
|
FINISHED |
| Object | approximately 2 metres |
—
|
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: approximately 2 metres | Statement: [Rauma-class fast attack craft, hasDraught, approximately 2 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDraught Context triple: [Rauma-class fast attack craft, hasDraught, approximately 2 metres]
-
A.
draught
Indicates that one entity is the version or serving of a beverage (typically beer) that is drawn from a cask, keg, or tap rather than from a bottle or can.
-
B.
hasDraft
Indicates that one entity possesses or is associated with a preliminary or unfinished version of another entity.
-
C.
isReadyToDrink
Indicates that a beverage or liquid is in a suitable state or condition for immediate consumption.
-
D.
hasDust
Indicates that one entity possesses, contains, or is covered with dust.
-
E.
drinkingPermitted
Indicates that consuming alcoholic beverages is allowed in a given context, location, or situation.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc616a01f48190b8bbde0e898a38c7 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5d6e54808190af4156edd4c8ffbc |
completed | March 31, 2026, 11:49 p.m. |
Created at: March 30, 2026, 6:53 p.m.