Triple
T15459269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Marino, California |
E371853
|
entity |
| Predicate | propertyValuesRank |
P59486
|
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, propertyValuesRank, among highest in Los Angeles County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyValuesRank Context triple: [San Marino, California, propertyValuesRank, among highest in Los Angeles County]
-
A.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
B.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
C.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
D.
rankingScope
chosen
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
E.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f1623f0819086f6fc2bfd536609 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:32 a.m.