Triple
T4035840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 26 frigate |
E83824
|
entity |
| Predicate | missionBayCapacity |
P53584
|
FINISHED |
| Object | boats |
—
|
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: boats | Statement: [Type 26 frigate, missionBayCapacity, boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionBayCapacity Context triple: [Type 26 frigate, missionBayCapacity, boats]
-
A.
pilgrimCapacity
Indicates the maximum number of pilgrims that an entity (such as a facility, vehicle, or location) is designed or allowed to accommodate.
-
B.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
C.
lifeboatCapacity
Indicates the maximum number of people or load that a lifeboat is designed and certified to safely carry.
-
D.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
-
E.
offersCapacityRange
Indicates that an entity provides or makes available a service, product, or resource whose capacity is specified as a range between a minimum and maximum value.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb132f6c8190937acd35a6a5a9e4 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:36 p.m.