Triple
T4914383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford Castle |
E110311
|
entity |
| Predicate | prisonFunctionStart |
P59412
|
FINISHED |
| Object | 13th century (approximate) |
—
|
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 (approximate) | Statement: [Oxford Castle, prisonFunctionStart, 13th century (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prisonFunctionStart Context triple: [Oxford Castle, prisonFunctionStart, 13th century (approximate)]
-
A.
prisonRole
Indicates a role or function that an entity holds within the context or system of a prison.
-
B.
hasPrison
Indicates that one entity possesses, contains, or is the location of a prison associated with another entity.
-
C.
prisonType
Indicates the specific category or classification of a prison associated with an entity.
-
D.
imprisonedFor
Indicates that one entity is held in detention or jail as a consequence of, or in connection with, a specific reason, action, or offense committed by another entity or itself.
-
E.
usedForImprisoning
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9f12b48190b3cb5378958d03cd |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6cc228088190849f23b7bd4cf549 |
completed | March 20, 2026, 3:50 p.m. |
Created at: March 20, 2026, 1:29 p.m.