Triple
T25921198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inchmahome |
E653174
|
entity |
| Predicate | foundedAsReligiousSiteInCentury |
P168043
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Inchmahome, foundedAsReligiousSiteInCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsReligiousSiteInCentury Context triple: [Inchmahome, foundedAsReligiousSiteInCentury, 13th century]
-
A.
foundedAsTempleInYear
Indicates that an entity was originally established as a temple in a specific year.
-
B.
foundedOnSiteOf
Indicates that something was established or built at the same physical location where another, earlier entity or structure previously existed.
-
C.
successorReligionAtSite
Indicates that one religion historically replaced or followed another as the primary religion practiced at a specific site.
-
D.
foundedTemple
Indicates that an entity established or created a temple, typically as its founder.
-
E.
hasReligiousSite
Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
- F. None of above. chosen
Provenance (4 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 22, 2026, 8:32 a.m.