Triple
T26571626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ossuary |
E666840
|
entity |
| Predicate | locatedAtSiteType |
P170237
|
FINISHED |
| Object | archaeological site |
—
|
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: archaeological site | Statement: [The Ossuary, locatedAtSiteType, archaeological site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtSiteType Context triple: [The Ossuary, locatedAtSiteType, archaeological site]
-
A.
isTypeSiteOf
chosen
Indicates that a site serves as the specific location or setting where a particular type, category, or classification is realized or occurs.
-
B.
locatedOnStructureType
Indicates that an entity is situated on or supported by a particular type of structure.
-
C.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
D.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 27, 2026, 1:58 a.m.