Triple
T7811090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whalley Abbey ruins |
E180684
|
entity |
| Predicate | dateOfFirstMention |
P4114
|
FINISHED |
| Object | late 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: late 13th century | Statement: [Whalley Abbey ruins, dateOfFirstMention, late 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstMention Context triple: [Whalley Abbey ruins, dateOfFirstMention, late 13th century]
-
A.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
B.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
C.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
D.
firstAppeared
chosen
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
E.
firstCelebratedInYear
Indicates the year in which something (such as an event, holiday, or celebration) was first observed or celebrated.
- 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78cd1cc8190b4cdd9850e1e2bb7 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:37 p.m.