Triple
T26004708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Brutus |
E646726
|
entity |
| Predicate | bucketCapacity |
P80385
|
FINISHED |
| Object | about 90 cubic yards |
—
|
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: about 90 cubic yards | Statement: [Big Brutus, bucketCapacity, about 90 cubic yards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bucketCapacity Context triple: [Big Brutus, bucketCapacity, about 90 cubic yards]
-
A.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
B.
unitCapacity
chosen
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
C.
unitOfCapacity
Indicates that one entity is a unit used to measure the capacity or volume of another entity.
-
D.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
E.
bootCapacity
Indicates the storage volume or carrying capacity available in the boot (trunk) of a vehicle.
- F. None of above.
Provenance (3 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057964948190b3ecab50a47a5e7c |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9 a.m.