Triple
T18511867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inns of Chancery |
E452360
|
entity |
| Predicate | ceasedToFunctionAsOriginallyIntended |
P41617
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Inns of Chancery, ceasedToFunctionAsOriginallyIntended, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedToFunctionAsOriginallyIntended Context triple: [Inns of Chancery, ceasedToFunctionAsOriginallyIntended, 19th century]
-
A.
defunct
chosen
Indicates that an entity has ceased to exist, operate, or function and is no longer active or in use.
-
B.
endedFunctionallyWith
Indicates that a process, event, or relationship has effectively concluded in practice, even if it has not been formally or officially terminated.
-
C.
defunctBy
Indicates that an entity has ceased to exist, operate, or function as a result of the actions, decisions, or influence of another entity.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
notDesignedAs
Indicates that one entity was not created, intended, or purposed to serve as or function as the other entity.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5334640888190bd44bc15e97822d3 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.