Triple
T24846532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rancho Los Feliz |
E621760
|
entity |
| Predicate | preAmericanOwnerFamily |
P156383
|
FINISHED |
| Object | Feliz family |
—
|
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: Feliz family | Statement: [Rancho Los Feliz, preAmericanOwnerFamily, Feliz family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preAmericanOwnerFamily Context triple: [Rancho Los Feliz, preAmericanOwnerFamily, Feliz family]
-
A.
formerOwnerFamily
chosen
Indicates that a member of the subject’s family previously owned the object but no longer does.
-
B.
historicalFamily
Indicates a familial relationship that existed between entities in the past, regardless of whether it still holds in the present.
-
C.
ownsByFamily
Indicates that ownership of an entity is held collectively or primarily by a family rather than by an individual or non-family organization.
-
D.
foundedByFamily
Indicates that an organization, institution, or entity was established by one or more members of the same family.
-
E.
foundingAncestor
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
- 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_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:20 a.m.