Triple
T36103058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesnaya |
E1044270
|
entity |
| Predicate | hasStationDepthCategory |
P126246
|
FINISHED |
| Object | deep-level |
—
|
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: deep-level | Statement: [Lesnaya, hasStationDepthCategory, deep-level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStationDepthCategory Context triple: [Lesnaya, hasStationDepthCategory, deep-level]
-
A.
hasWaterDepthCategory
Indicates the classification of something based on the range or category of its water depth.
-
B.
lineCStationDepth
chosen
Indicates that a particular station on a transit line is located at a specified depth (or vertical position) relative to a reference level.
-
C.
deepestStationDepthMeters
Indicates the maximum depth, in meters, reached by any station associated with the subject.
-
D.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
E.
deepestStation
Indicates that one station in a network or system is located at a greater depth (e.g., below ground or sea level) than all other stations.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: May 3, 2026, 4:08 p.m.