Triple
T24846515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rancho Los Feliz |
E621760
|
entity |
| Predicate | formsHistoricalBasisOf |
P1823
|
FINISHED |
| Object | Los Feliz neighborhood |
—
|
NE NERFINISHED |
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: Los Feliz neighborhood | Statement: [Rancho Los Feliz, formsHistoricalBasisOf, Los Feliz neighborhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsHistoricalBasisOf Context triple: [Rancho Los Feliz, formsHistoricalBasisOf, Los Feliz neighborhood]
-
A.
historicalOrigin
chosen
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
B.
historicalBackground
Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
-
C.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
D.
historicallyBasedOn
Indicates that something is derived from, inspired by, or modeled on historical events, sources, or precedents.
-
E.
sharesHistoricalLegacyOf
Indicates that one entity is connected to, or participates in, the same historical legacy, tradition, or heritage as another entity.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:20 a.m.