Triple
T1436264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eden Gardens |
E30567
|
entity |
| Predicate | formerCapacity |
P29291
|
FINISHED |
| Object | over 100,000 |
—
|
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: over 100,000 | Statement: [Eden Gardens, formerCapacity, over 100,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCapacity Context triple: [Eden Gardens, formerCapacity, over 100,000]
-
A.
laterCapacity
Indicates that one entity’s capacity or capability occurs, becomes available, or is realized at a later time than another’s.
-
B.
originalCapacity
Indicates the initial or designed maximum amount or volume that something can hold, process, or produce before any changes or adjustments.
-
C.
installedCapacity
Indicates the maximum output or production capability that has been set up or built for a system, facility, or equipment, typically measured under specified conditions.
-
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.
formerCollectionOf
Indicates that an entity once served as a collection or repository for another entity, but no longer holds that role.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c5fd2c5c81909283b7a74aff89b7 |
completed | March 1, 2026, 11:04 p.m. |
Created at: March 1, 2026, 8 p.m.