Triple
T304814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan |
E6273
|
entity |
| Predicate | atmosphericPressure_surface_bar |
P2032
|
FINISHED |
| Object | 1.45 |
—
|
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: 1.45 | Statement: [Titan, atmosphericPressure_surface_bar, 1.45]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: atmosphericPressure_surface_bar Context triple: [Titan, atmosphericPressure_surface_bar, 1.45]
-
A.
hasAtmosphericPressureAtSeaLevel
chosen
Indicates that an entity possesses a specific value of atmospheric pressure measured at sea level.
-
B.
pressureAtBottom
Indicates that a specified amount of pressure is exerted or present at the bottom of a given object, container, or region.
-
C.
hasAtmosphere
Indicates that an astronomical body possesses a surrounding layer of gases held by its gravity.
-
D.
hasAverageSurfaceTemperature
Indicates that an entity is associated with a specific mean value of its surface temperature over a defined period or condition.
-
E.
surfaceTemperatureRange
Indicates the range between the minimum and maximum surface temperatures observed or allowed for an entity.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea11c4908190a8723033bdf6f479 |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.