Triple
T8073873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Pancras Old Church |
E188442
|
entity |
| Predicate | hasEarlierOrigin |
P3654
|
FINISHED |
| Object | medieval period |
—
|
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: medieval period | Statement: [St Pancras Old Church, hasEarlierOrigin, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlierOrigin Context triple: [St Pancras Old Church, hasEarlierOrigin, medieval period]
-
A.
hasEarlierVersion
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
-
B.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
C.
hasEarlierPhase
Indicates that one phase occurs before another phase in a process or sequence.
-
D.
hasHistoricalPrecursor
Indicates that one entity existed earlier and served as a predecessor, model, or influential forerunner to the other in a historical context.
-
E.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
- 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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb404a98408190b6c8eecb95ad086d |
completed | March 31, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:27 p.m.