Triple
T14846397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eassie |
E349101
|
entity |
| Predicate | stoneLocation |
P76038
|
FINISHED |
| Object | within church ruins |
—
|
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: within church ruins | Statement: [Eassie, stoneLocation, within church ruins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoneLocation Context triple: [Eassie, stoneLocation, within church ruins]
-
A.
mineLocation
Indicates that a specified location is the site where a particular mine (e.g., resource extraction or explosive device) is situated.
-
B.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
-
C.
objectLocation
chosen
Indicates that one entity is located at, in, or on another entity or spatial region.
-
D.
relicsLocatedIn
Indicates that certain relics are situated, stored, or found within a specific location.
-
E.
locationOfSee
Indicates a relationship where a particular place is the setting or site in which an act of seeing or visual perception occurs.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded29236dc8190b7d3a37d09f9fb21 |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:53 a.m.