Triple
T15535259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushroom Bridge |
E370322
|
entity |
| Predicate | hasEnvironmentElement |
P63681
|
FINISHED |
| Object | water under the bridge |
—
|
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: water under the bridge | Statement: [Mushroom Bridge, hasEnvironmentElement, water under the bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnvironmentElement Context triple: [Mushroom Bridge, hasEnvironmentElement, water under the bridge]
-
A.
hasEnvironmentType
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
B.
hasElementType
chosen
Indicates that something is composed of or contains elements that are of a specified type.
-
C.
hasEnvironmentalFunction
Indicates that an entity serves a specific role or purpose related to the environment, such as contributing to ecological processes, protection, or sustainability.
-
D.
isEnvironmentOf
Indicates that one entity serves as the surrounding conditions, context, or setting in which another entity exists, operates, or occurs.
-
E.
hasPrimaryEnvironment
Indicates that an entity is associated with its main or most characteristic environment or setting.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.