Triple
T1393478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester Cathedral |
E30612
|
entity |
| Predicate | earliestReference |
P3921
|
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: [Manchester Cathedral, earliestReference, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestReference Context triple: [Manchester Cathedral, earliestReference, 13th century]
-
A.
earliestKnownHolder
Indicates that the subject is the first known entity in time to have possessed, held, or been assigned the object.
-
B.
earliestTextsIn
Indicates that certain texts are among the earliest known examples found in or associated with a particular place or context.
-
C.
earliestState
Indicates that one state or condition occurs before all other related states in time, representing the earliest point in a sequence.
-
D.
firstClearlyAttestedIn
chosen
Indicates the earliest known point in time or source where something is clearly documented or evidenced.
-
E.
locationOfEarlyUse
Indicates the place where something was first or among the earliest instances to be used or applied.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c37cd99081908d16014e0b99992d |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.