Triple
T21139407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brugmann's law |
E520890
|
entity |
| Predicate | hasEnvironmentCondition |
P126032
|
FINISHED |
| Object | open syllable |
—
|
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: open syllable | Statement: [Brugmann's law, hasEnvironmentCondition, open syllable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnvironmentCondition Context triple: [Brugmann's law, hasEnvironmentCondition, open syllable]
-
A.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
B.
hasEnvironmentType
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
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.
hasApproachEnvironment
Indicates that an entity uses, is associated with, or is designed for a particular environment or context in which it operates or approaches something.
-
E.
hasEnvironmentalAttribute
chosen
Indicates that an entity possesses a specific environmental property, condition, or characteristic.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235e389881908813909e05d1413a |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:57 p.m.