Triple
T5593914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Register of Historical Resources |
E146947
|
entity |
| Predicate | typeOfProtectedResource |
P64956
|
FINISHED |
| Object | historic building |
—
|
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: historic building | Statement: [California Register of Historical Resources, typeOfProtectedResource, historic building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfProtectedResource Context triple: [California Register of Historical Resources, typeOfProtectedResource, historic building]
-
A.
typeOfGrant
Indicates the specific category or kind of grant associated with an entity.
-
B.
grantType
Indicates the specific authorization or credential flow used to obtain access or permissions in a grant-based process.
-
C.
bearerType
Indicates the type or category of entity that serves as the bearer or holder in a given relationship or context.
-
D.
credentialType
Indicates the specific kind or category of credential associated with an entity or relationship.
-
E.
authenticationType
Indicates the method or mechanism used to verify and confirm an entity’s identity in an interaction or system.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020bc41408190bc990da8ddeb931e |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:38 p.m.