Triple
T31979375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Court House, Ruthin |
E816534
|
entity |
| Predicate | usedToServeAs |
P2417
|
FINISHED |
| Object | court house |
—
|
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: court house | Statement: [Old Court House, Ruthin, usedToServeAs, court house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToServeAs Context triple: [Old Court House, Ruthin, usedToServeAs, court house]
-
A.
possiblyServedAs
Indicates that an entity may have held or fulfilled a particular role, position, or function, but this service is uncertain or not definitively confirmed.
-
B.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
C.
historicallyUsedFor
chosen
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
formerlyUsedBy
Indicates that an entity was used by another entity in the past but is no longer in use by that entity.
-
E.
alsoServesAs
Indicates that one entity has an additional role, function, or identity that it fulfills simultaneously with its primary 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 12:11 a.m.