Triple
T4269918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollywood Historic District |
E96916
|
entity |
| Predicate | hasNRHPStatus |
P43168
|
FINISHED |
| Object | listed |
—
|
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: listed | Statement: [Hollywood Historic District, hasNRHPStatus, listed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNRHPStatus Context triple: [Hollywood Historic District, hasNRHPStatus, listed]
-
A.
monumentStatus
Indicates the official designation or condition of an entity as a monument, such as whether it is recognized, protected, or classified under heritage or preservation status.
-
B.
designatedNRHP
chosen
Indicates that an entity has been formally designated and listed on the National Register of Historic Places (NRHP).
-
C.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
D.
addedToNRHP
Indicates that something has been officially listed on the National Register of Historic Places.
-
E.
NRHPReferenceNumber
Indicates the unique identification number assigned to a property or site listed in the National Register of Historic Places.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ffa30c08190913622ffec47d33d |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.