Triple
T14842155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Exchange and Provost Dungeon |
E348989
|
entity |
| Predicate | functionAfterRevolution |
P86024
|
FINISHED |
| Object | post office |
—
|
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: post office | Statement: [Old Exchange and Provost Dungeon, functionAfterRevolution, post office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionAfterRevolution Context triple: [Old Exchange and Provost Dungeon, functionAfterRevolution, post office]
-
A.
functionDuringRevolution
Indicates that an entity performs or serves a particular function specifically during a revolutionary period or event.
-
B.
functionAfterReformation
Indicates that one function or role exists or is performed in the state or period following a process of reformation or reform.
-
C.
postRevolution
Indicates that one event, condition, or state occurs or exists after a revolution has taken place.
-
D.
functionAfterCivilWar
Indicates that one entity serves or operates in a particular function, role, or capacity following the end of a civil war.
-
E.
postRevolutionStatus
chosen
Indicates the condition, role, or state an entity holds after a revolution has occurred.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded28fa49c81908d1059e6cafd607f |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:53 a.m.