Triple
T16911320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verrückt |
E410199
|
entity |
| Predicate | capacityPerRaft |
P80385
|
FINISHED |
| Object | three riders |
—
|
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: three riders | Statement: [Verrückt, capacityPerRaft, three riders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityPerRaft Context triple: [Verrückt, capacityPerRaft, three riders]
-
A.
capacityRecord
Indicates a recorded measure of how much of a resource, space, or system is available or can be utilized at a given time.
-
B.
capacityPerSide
Indicates the maximum quantity or volume that each individual side or unit in a pair can hold or accommodate.
-
C.
unitCapacity
chosen
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
D.
ramCapacity
Indicates the amount of system memory (RAM) that an entity possesses or supports.
-
E.
capacityCategory
Indicates the classification of something based on the amount or volume it can hold, handle, or accommodate.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca3d6be88190bca5e1fdf727141b |
completed | April 18, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.