Triple
T25625335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford family |
E642412
|
entity |
| Predicate | hasFamilyGrave |
P78565
|
FINISHED |
| Object | Stanford family mausoleum at Stanford University |
—
|
NE NERFINISHED |
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: Stanford family mausoleum at Stanford University | Statement: [Stanford family, hasFamilyGrave, Stanford family mausoleum at Stanford University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyGrave Context triple: [Stanford family, hasFamilyGrave, Stanford family mausoleum at Stanford University]
-
A.
hasGravestone
Indicates that one entity possesses, is associated with, or is commemorated by a gravestone.
-
B.
hasGraveOrMemorialOf
chosen
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
-
C.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
D.
hasTypeOfGrave
Indicates that an entity is associated with a specific kind or category of grave.
-
E.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 5:08 p.m.