Triple
T2234975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ligeia Mare |
E49257
|
entity |
| Predicate | pressureCondition |
P20809
|
FINISHED |
| Object | about 1.5 bar at Titan surface |
—
|
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: about 1.5 bar at Titan surface | Statement: [Ligeia Mare, pressureCondition, about 1.5 bar at Titan surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressureCondition Context triple: [Ligeia Mare, pressureCondition, about 1.5 bar at Titan surface]
-
A.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
-
B.
pressurization
Indicates the process of applying or maintaining pressure on or within an object, system, or environment.
-
C.
surfacePressure
chosen
Indicates the pressure exerted by a fluid (such as air or water) on the surface of an object or body.
-
D.
pressureAtBottom
Indicates that a specified amount of pressure is exerted or present at the bottom of a given object, container, or region.
-
E.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc09297a481909e8fe6ec645de616 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.