Triple
T4947675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boyle's law |
E111089
|
entity |
| Predicate | approximateValidity |
P32406
|
FINISHED |
| Object | low pressure gases |
—
|
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: low pressure gases | Statement: [Boyle's law, approximateValidity, low pressure gases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateValidity Context triple: [Boyle's law, approximateValidity, low pressure gases]
-
A.
validityType
chosen
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
B.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
C.
hasValidity
Indicates that something possesses a period or condition during which it is considered legally, logically, or functionally acceptable or in force.
-
D.
hasValidityPeriod
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
-
E.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd716520f08190862249efb2058fd4 |
completed | March 20, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.