Triple
T10894659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evergreen Cemetery, Oakland |
E257275
|
entity |
| Predicate | hasEstablishedDate |
P9196
|
FINISHED |
| Object | unknown |
—
|
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: unknown | Statement: [Evergreen Cemetery, Oakland, hasEstablishedDate, unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEstablishedDate Context triple: [Evergreen Cemetery, Oakland, hasEstablishedDate, unknown]
-
A.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
B.
establishedAt
chosen
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
C.
establishedTo
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
-
D.
establishedThrough
Indicates that a relationship, structure, or state comes into existence or is formally created by means of a specified process, action, or intermediary.
-
E.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d0153408190bcba2d9b03d78804 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.