Triple
T3119851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Hall (Manchester Town Hall) |
E65154
|
entity |
| Predicate | completionPeriod |
P45474
|
FINISHED |
| Object | late 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: late 19th century | Statement: [Great Hall (Manchester Town Hall), completionPeriod, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completionPeriod Context triple: [Great Hall (Manchester Town Hall), completionPeriod, late 19th century]
-
A.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
B.
completionRate
Indicates the proportion of a task, process, or set of items that has been finished relative to its total intended amount.
-
C.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
D.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
E.
completedBefore
Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4eb6a6081909df41f67999eb4ff |
completed | March 8, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.