Triple
T26052916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of Commerce |
E648033
|
entity |
| Predicate | hasCompletionEra |
P53319
|
FINISHED |
| Object | early 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: early 20th century | Statement: [Cathedral of Commerce, hasCompletionEra, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompletionEra Context triple: [Cathedral of Commerce, hasCompletionEra, early 20th century]
-
A.
approximateCompletionEra
chosen
Indicates the general historical period or time range during which something was completed, without specifying an exact date.
-
B.
endedEra
Indicates that one entity brought about or marked the conclusion of a particular era associated with another entity.
-
C.
hasEraReset
Indicates that a new era or time period has been initiated, resetting the previous temporal sequence or counting.
-
D.
hasPublicationEra
Indicates the time period or era during which a publication was released or made publicly available.
-
E.
hasEraInfluence
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 22, 2026, 9:11 a.m.