Triple
T37901165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garber-Wellington aquifer system |
E945413
|
entity |
| Predicate | developedForUseSince |
P36578
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Garber-Wellington aquifer system, developedForUseSince, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedForUseSince Context triple: [Garber-Wellington aquifer system, developedForUseSince, early 20th century]
-
A.
developedSince
chosen
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
-
B.
developedAt
Indicates the place or location where something was created, built, or developed.
-
C.
dateImplemented
Indicates the date on which something (such as a plan, rule, feature, or system) was put into effect or made operational.
-
D.
developmentDate
Indicates the date on which something was created, developed, or brought into existence.
-
E.
developedBetween
Indicates a relationship that was created, evolved, or came into existence between two entities over a period of time.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:20 p.m.