Triple
T5826335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Cook Memorial Jet |
E129234
|
entity |
| Predicate | pumpingCapacity |
P1931
|
FINISHED |
| Object | up to 500 litres per second |
—
|
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: up to 500 litres per second | Statement: [Captain Cook Memorial Jet, pumpingCapacity, up to 500 litres per second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pumpingCapacity Context triple: [Captain Cook Memorial Jet, pumpingCapacity, up to 500 litres per second]
-
A.
pumpingPower
Indicates the rate at which energy is supplied or transferred by a pump to move a fluid or medium.
-
B.
capacityPerHour
Indicates the maximum amount of output or throughput an entity can handle or produce in one hour.
-
C.
numberOfPumps
Indicates the quantity of pumps associated with or required by an entity or system.
-
D.
typicalCapacity
chosen
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
E.
annualCapacity
Indicates the maximum amount of output or throughput an entity can produce or handle within a one-year period.
- 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.