Triple
T6287069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactic thin disk |
E140925
|
entity |
| Predicate | hasFlaring |
P69903
|
FINISHED |
| Object | scale height increases with radius |
—
|
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: scale height increases with radius | Statement: [Galactic thin disk, hasFlaring, scale height increases with radius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlaring Context triple: [Galactic thin disk, hasFlaring, scale height increases with radius]
-
A.
hasPlume
Indicates that an entity possesses or exhibits a plume, such as a feathered tuft, spray, or column-like emission.
-
B.
hasFlanker
Indicates that an entity is positioned or assigned as a flanking support or protection alongside another entity.
-
C.
flameHeight
Indicates the vertical extent or height reached by a flame during burning.
-
D.
heightIncludingFlame
Indicates the total vertical height of something measured from its base to the top of its flame.
-
E.
hasPyrotechnics
Indicates that an entity includes, uses, or features pyrotechnic effects or fireworks as part of its characteristics or activities.
- F. None of above. chosen
Provenance (4 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063ff9f74819088dc603f56fc930c |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c0560a0270819098ad2785b91e8f39 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05b37ac1881909e947822490ba4f2 |
completed | March 22, 2026, 9:12 p.m. |
Created at: March 22, 2026, 4:26 p.m.