Triple
T23414722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huygens Gap |
E560171
|
entity |
| Predicate | isNarrowComparedTo |
P11452
|
FINISHED |
| Object | wider regions of Cassini Division |
—
|
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: wider regions of Cassini Division | Statement: [Huygens Gap, isNarrowComparedTo, wider regions of Cassini Division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNarrowComparedTo Context triple: [Huygens Gap, isNarrowComparedTo, wider regions of Cassini Division]
-
A.
isNarrow
Indicates that something has a small width or limited breadth relative to a reference or context.
-
B.
hasNarrowestWidth
Indicates that one entity has the smallest width dimension compared to a specified set of entities or alternatives.
-
C.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
D.
smallerThan
chosen
Indicates that one entity has a strictly lesser size, dimension, or magnitude than another entity.
-
E.
isNarrowestPartOf
Indicates that one entity constitutes the slimmest or most constricted section within the extent or structure of another 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a514b1d08190bbde2c3714c996fd |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:39 p.m.