Triple
T20094762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messier 101 |
E496369
|
entity |
| Predicate | numberOfSpiralArms |
P132913
|
FINISHED |
| Object | multiple prominent spiral arms |
—
|
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: multiple prominent spiral arms | Statement: [Messier 101, numberOfSpiralArms, multiple prominent spiral arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSpiralArms Context triple: [Messier 101, numberOfSpiralArms, multiple prominent spiral arms]
-
A.
hasSpiralArmCount
chosen
Indicates the number of spiral arms that a spiral-structured entity possesses.
-
B.
hasSpiralArms
Indicates that the subject possesses spiral-shaped arm-like structures extending outward, typically arranged in a winding or coiled pattern.
-
C.
isMajorSpiralArmOf
Indicates that one spiral arm is a primary, large-scale arm structure belonging to or forming a main component of a spiral galaxy.
-
D.
hasNoProminentSpiralArms
Indicates that the object lacks clearly defined or visually dominant spiral arm structures.
-
E.
numberOfMainGalaxies
Indicates the count of primary or central galaxies associated with a given system or context.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666b891c8190b4e4a60b73728771 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:23 p.m.