Triple
T18973386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Zellerbach Corporation |
E464228
|
entity |
| Predicate | Crown Zellerbach BuildingCompletion |
P134004
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [Crown Zellerbach Corporation, Crown Zellerbach BuildingCompletion, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Crown Zellerbach BuildingCompletion Context triple: [Crown Zellerbach Corporation, Crown Zellerbach BuildingCompletion, 1959]
-
A.
locatedInBuildingCompletedIn
Indicates that something is situated within a building that was completed in a specific year or time period.
-
B.
courthouseCompletedIn
Indicates the year or date when a courthouse building was finished and became structurally complete.
-
C.
churchConstructionCompleted
Indicates that the process of building or constructing a church has been finished.
-
D.
towerCompleted
Indicates that the construction of a tower has been fully finished and reached its intended completed state.
-
E.
Troy Savings Bank building
Indicates that one entity is a building associated with, owned by, or used as premises for the Troy Savings Bank.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d61d7728819096f0baea75658a6a |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, noon