Triple
T3372785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Marino, California |
E70992
|
entity |
| Predicate | propertyValues |
P7345
|
FINISHED |
| Object | among highest in Los Angeles County |
—
|
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: among highest in Los Angeles County | Statement: [San Marino, California, propertyValues, among highest in Los Angeles County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyValues Context triple: [San Marino, California, propertyValues, among highest in Los Angeles County]
-
A.
eligibleProperties
Indicates that certain properties meet the required conditions or criteria to qualify for a specified purpose or status.
-
B.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
C.
metaProperty
Indicates that one property functions as a higher-level descriptor or attribute about another property, rather than about an entity directly.
-
D.
value
chosen
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
-
E.
isValuePriced
Indicates that something is offered at a relatively low or favorable price compared to typical or premium alternatives.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2bdcf70819087fc7e00fbd61e0d |
completed | March 8, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.