Triple
T1353682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melrose Abbey |
E28938
|
entity |
| Predicate | partiallyRebuiltInCentury |
P27944
|
FINISHED |
| Object | 14th 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: 14th century | Statement: [Melrose Abbey, partiallyRebuiltInCentury, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyRebuiltInCentury Context triple: [Melrose Abbey, partiallyRebuiltInCentury, 14th century]
-
A.
rebuiltInCentury
Indicates that an existing structure or entity was reconstructed or significantly rebuilt during a specified century.
-
B.
compiledInCentury
Indicates that something (such as a work, text, or document) was compiled during a specified century.
-
C.
constructionCentury
Indicates the century during which something was constructed or built.
-
D.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
-
E.
largelyRebuilt
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26e916c8190b4b324df87f4c121 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c20fd1fc8190977a768b1ed2d23b |
completed | March 1, 2026, 10:47 p.m. |
Created at: March 1, 2026, 7:56 p.m.