Triple
T28850329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamboville Cemetery |
E728573
|
entity |
| Predicate | inUseFor |
P98
|
FINISHED |
| Object | burials |
—
|
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: burials | Statement: [Tamboville Cemetery, inUseFor, burials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUseFor Context triple: [Tamboville Cemetery, inUseFor, burials]
-
A.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
isSometimesUsedFor
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
-
C.
usedForProduct
Indicates that one entity serves as a tool, component, or means specifically employed in the creation, operation, or delivery of another entity considered as a product.
-
D.
isBelievedToBeUsedFor
Indicates that something is thought or assumed to serve a particular purpose or function, without certainty.
-
E.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659d855b4819099e9c239051edafe |
completed | May 2, 2026, 8:08 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:43 a.m.