Triple
T17660666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York Castle |
E440241
|
entity |
| Predicate | usedAsLawCourtsUntil |
P128442
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [York Castle, usedAsLawCourtsUntil, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsLawCourtsUntil Context triple: [York Castle, usedAsLawCourtsUntil, late 20th century]
-
A.
usedInCourts
Indicates that something is employed or applied within legal court settings, such as in judicial proceedings or courtroom processes.
-
B.
usedCourt
Indicates that an entity made use of or participated in legal proceedings within a particular court.
-
C.
usedByCourt
Indicates that something (such as a document, argument, or evidence) is utilized or relied upon by a court in its judicial process.
-
D.
usedAsCityHallUntil
Indicates that a building or location functioned as the city hall up to a specified end date or time period.
-
E.
supremeCourtUseFrom
Indicates that a decision, precedent, or legal principle is utilized or drawn upon by a supreme court from a particular source.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea5270c81909d374c9e3946cea6 |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 9:42 a.m.