Triple
T27064763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALRV streetcar |
E685142
|
entity |
| Predicate | capacityComparedToCLRV |
P31373
|
FINISHED |
| Object | higher |
—
|
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: higher | Statement: [ALRV streetcar, capacityComparedToCLRV, higher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityComparedToCLRV Context triple: [ALRV streetcar, capacityComparedToCLRV, higher]
-
A.
scaleComparison
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
B.
capacityCategory
Indicates the classification of something based on the amount or volume it can hold, handle, or accommodate.
-
C.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
D.
capacityRank
chosen
Indicates the relative ordering of entities based on how much capacity (e.g., volume, throughput, or capability) they possess compared to others.
-
E.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622e809748190bfc40b8cee0fa073 |
completed | May 2, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:24 a.m.