Triple
T4956933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Edmund Hall, Oxford |
E111304
|
entity |
| Predicate | foundedAsHall |
P364
|
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 Edmund Hall, Oxford, foundedAsHall, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsHall Context triple: [St Edmund Hall, Oxford, foundedAsHall, medieval period]
-
A.
foundedAs
chosen
Indicates the original name or form under which an organization, institution, or entity was first established.
-
B.
foundedOnSiteOf
Indicates that something was established or built at the same physical location where another, earlier entity or structure previously existed.
-
C.
foundedAsMuseumBy
Indicates that an entity was established or created as a museum by a specific person or organization.
-
D.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
E.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71d6ba9c8190932f8d81240c3f56 |
completed | March 20, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:32 p.m.