Triple
T35098277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles |
E1012928
|
entity |
| Predicate | waterSourceDistance |
P195062
|
FINISHED |
| Object | distant river basin |
—
|
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: distant river basin | Statement: [Los Angeles, waterSourceDistance, distant river basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSourceDistance Context triple: [Los Angeles, waterSourceDistance, distant river basin]
-
A.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
B.
waterSourceAccessibility
Indicates how easily and reliably water sources can be reached, obtained, and used by intended users.
-
C.
waterSourceDedicatedTo
Indicates that a particular water source is specifically allocated or reserved for a designated use, group, or purpose.
-
D.
waterSourceType
Indicates the kind or category of source from which water is obtained.
-
E.
waterSourceAfter
Indicates that one water source occurs, appears, or is accessed after another in time or sequence.
- F. None of above. chosen
Provenance (4 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
| PDg | Predicate description generation | batch_69fd9fef7aac819089cc88dd3d00296d |
completed | May 8, 2026, 8:33 a.m. |
Created at: May 3, 2026, 4:01 p.m.