Triple
T18772999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Hot Cavity |
E459061
|
entity |
| Predicate | hasGasDensity |
P100440
|
FINISHED |
| Object | low |
—
|
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 | Statement: [Local Hot Cavity, hasGasDensity, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGasDensity Context triple: [Local Hot Cavity, hasGasDensity, low]
-
A.
hasMeanDensity
Indicates that one entity possesses a specified average mass per unit volume (mean density).
-
B.
givesDensityOf
Indicates that one entity provides or specifies the density value of another entity.
-
C.
hasGasMass
Indicates that an entity possesses a specified amount of gas mass as one of its physical properties.
-
D.
hasDensityParameter
chosen
Indicates that an entity is associated with a specific density-related parameter or value used to characterize its density properties.
-
E.
containsGasField
Indicates that one entity geographically includes or encompasses a gas field within its boundaries.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e593378a4081909cc1b0856fce7d7d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.