Triple
T14758426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer, California |
E346790
|
entity |
| Predicate | hasTypicalHousing |
P40076
|
FINISHED |
| Object | single-family homes |
—
|
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: single-family homes | Statement: [Pioneer, California, hasTypicalHousing, single-family homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalHousing Context triple: [Pioneer, California, hasTypicalHousing, single-family homes]
-
A.
typicalHouse
Indicates that something is a standard or representative example of a house in terms of its usual features, structure, or characteristics.
-
B.
hasHousingArrangement
Indicates that an entity has a specific type or status of housing or living arrangement in relation to another entity or context.
-
C.
hasGeneralHouse
Indicates that an entity possesses or is associated with a general-purpose house or primary residential building.
-
D.
housingPattern
chosen
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or context.
-
E.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f0f5a48190af008352c26574d7 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.