Triple
T32858093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strataca |
E840433
|
entity |
| Predicate | undergroundEnvironment |
P42731
|
FINISHED |
| Object | dry |
—
|
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: dry | Statement: [Strataca, undergroundEnvironment, dry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergroundEnvironment Context triple: [Strataca, undergroundEnvironment, dry]
-
A.
undergroundZone
Indicates that something is located in, associated with, or occurring within an area beneath the ground surface.
-
B.
subterranean
chosen
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
C.
integratedIntoUnderground
Indicates that something has been incorporated or absorbed into an underground system, structure, or environment.
-
D.
enteredUndergroundService
Indicates that an entity has begun operating or functioning within an underground system or environment.
-
E.
undergroundBranch
Indicates that one entity is a branch or extension of another that operates or exists in a hidden, secret, or non-public manner.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 1, 2026, 1:17 a.m.