Triple
T33310362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Celtic |
E852859
|
entity |
| Predicate | classCapacityFirst |
P177808
|
FINISHED |
| Object | 347 |
—
|
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: 347 | Statement: [SS Celtic, classCapacityFirst, 347]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classCapacityFirst Context triple: [SS Celtic, classCapacityFirst, 347]
-
A.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
B.
originalCapacity
Indicates the initial or designed maximum amount or volume that something can hold, process, or produce before any changes or adjustments.
-
C.
currentCapacity
Indicates the present amount of capacity an entity is using or able to provide at a given time.
-
D.
laterCapacity
Indicates that one entity’s capacity or capability occurs, becomes available, or is realized at a later time than another’s.
-
E.
hasCapacityTo
Indicates that one entity possesses the ability, power, or potential to perform an action or bring about a particular effect in relation to another entity or context.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:33 a.m.