Triple
T33439544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marian apparitions of 1877 |
E856322
|
entity |
| Predicate | hasLocationAtTime |
P121592
|
FINISHED |
| Object | Kingdom of Prussia |
—
|
NE NERFINISHED |
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: Kingdom of Prussia | Statement: [Marian apparitions of 1877, hasLocationAtTime, Kingdom of Prussia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationAtTime Context triple: [Marian apparitions of 1877, hasLocationAtTime, Kingdom of Prussia]
-
A.
locatedAtTime
chosen
Indicates that a location relationship holds during a specific time or time interval.
-
B.
hasTemporalLocation
Indicates that something occurs, exists, or is valid during a specific time or time interval.
-
C.
hasLocationOnDay
Indicates that an entity is located at a specific place on a particular calendar day.
-
D.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
E.
previousLocationTime
Indicates the specific time at which an entity was located at its immediately preceding location before its current one.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: May 1, 2026, 1:37 a.m.